JuliaDynamics / JuliaDynamics/ConcurrentSim.jl

verify all basic types are concrete (and consider using sumtypes where possible)

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Julia is not fast when working with containers over abstract types. In particular, the heap and other fields in the Simulation type are currently abstractly typed or have abstract eltypes. We need a thorough cleanup here, to ensure we do not introduce unnecessary slowdowns.

The first step is to verify that Simulation and its fields are all fully concrete (recursively into the type of each field). The biggest offender is the heap.

The second step would be to verify this for the rest of the major types introduced in the library.

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 by inspecting the definition of the Simulation type, its fields, and especially the heap and their recursive element types. Verify that Simulation and the other major library types are fully concrete, then assess where sum types could replace abstract types without introducing unnecessary slowdowns.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
performance
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.