SciML / SciML/RuntimeGeneratedFunctions.jl

Debugging generated functions

Open
#24 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
112
Forks
19
Avg merge
6h 11m
Merged PRs (30d)
9

Description

@ChrisRackauckas mentioned that to get a nice stack trace from generated functions, we can print the expression into a temporary file and point the stack trace to that file.

Can this be done automatically with Ctrl - Q functionality in the REPL and other IDEs?

CC: @pfitzseb, @c42f

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 investigating how generated expressions could be printed to temporary files and how stack traces can point to those files. Then examine the REPL and IDE Ctrl-Q workflows, define behavior across those environments, and validate that the resulting stack traces are useful; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
developer-experience
Issue type
Feature
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.