You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[question] function signature changed, revise here or upto downstream? #152
one function add_active_gotos! has changed the number of arguments it accepts - with the result that downstream that uses LoweredCodeUtils now may break: a common setup is to have both Revise.jl and JET.jl, both of them uses LoweredCodeUtils but with default/no [compat] section, it would update LoweredCodeUtils to 3.6.0, and break JET.jl aviatesk/JET.jl#823
Is it better/more up to downstream to pin a version/change code, or is it better to add a default argument so the old 4-arg call without specifying controller still works?
JET v0.11.4 pins the LCU version. New versions of JET should be compatible with LCU v3.6 only.
JET compat with LCU 3.6 is tracked at aviatesk/JET.jl#827.
Activity
aviatesk commentedon Jun 20, 2026
JET v0.11.4 pins the LCU version. New versions of JET should be compatible with LCU v3.6 only.
JET compat with LCU 3.6 is tracked at aviatesk/JET.jl#827.
Let me know if you have any further questions!