Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@aggressive_constprop -> @constprop renaming hasn't been backported to 1.7 #17

Closed
stillyslalom opened this issue Sep 10, 2021 · 3 comments · Fixed by #18
Closed

@aggressive_constprop -> @constprop renaming hasn't been backported to 1.7 #17

stillyslalom opened this issue Sep 10, 2021 · 3 comments · Fixed by #18

Comments

@stillyslalom
Copy link

See JuliaLang/julia#41781 (comment)

Breaks downstream packages on 1.7 following e3e240c. Will need to more-carefully specify version bounds here:

@static if VERSION >= v"1.7.0-DEV.421"

@MasonProtter
Copy link

I got bit by this. Doing

]add Static@v0.3.1

solved the problem as a stopgap measure.

@ForceBru
Copy link

Same here:

Failed to precompile Symbolics [0c5d862f-8b57-4792-8d23-62f2024744c7] to /Users/forcebru/.julia/compiled/v1.7/Symbolics/jl_MDgUwq.
ERROR: LoadError: UndefVarError: @constprop not defined
Stacktrace:
 [1] top-level scope
   @ ~/.julia/packages/Static/cAyCC/src/Static.jl:10
 [2] include
   @ ./Base.jl:417 [inlined]
 [3] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt64}}, source::String)
   @ Base ./loading.jl:1318
 [4] top-level scope
   @ none:1
 [5] eval
   @ ./boot.jl:373 [inlined]
 [6] eval(x::Expr)
   @ Base.MainInclude ./client.jl:453
 [7] top-level scope
   @ none:1
in expression starting at /Users/forcebru/.julia/packages/Static/cAyCC/src/Static.jl:1

Julia 1.7.0-beta3.0

@Tokazama
Copy link
Collaborator

This seems to be somewhat recent and possibly urgent, so I'll try to attend to any PRs addressing this. Unfortunately I want be at a computer to personally address it until tomorrow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants