JuliaDynamics / JuliaDynamics/ConcurrentSim.jl

Try - catch bad for performance in Julia.

Open
#104 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement
Dominant language
Julia
Stars
198
Forks
40
Avg merge
21h 40m
Merged PRs (30d)
2

Description

From the official Julia documentation, in the section on noteworthy differences between Julia and Python:

Exception handling in Julia is done using try — catch — finally, instead of try — except — finally. In contrast to Python, it is not recommended to use exception handling as part of the normal workflow in Julia (compared with Python, Julia is faster at ordinary control flow but slower at exception-catching).

Therefore, while it makes sense for SimPy to handle interruptions with try - except logic, doing so in ConcurrentSim hurts performance, and may not be the ideal solution.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Julia documentation, then locate ConcurrentSim's exception-handling paths; no file, test, or entry point is named. Compare the current interruption handling with Julia's performance guidance and define completion around an evidence-backed improvement that preserves interruption behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
performance
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.