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

Deprecate eval and include, and recommend alternatives #279

Open
fonsp opened this issue Aug 12, 2020 · 0 comments
Open

Deprecate eval and include, and recommend alternatives #279

fonsp opened this issue Aug 12, 2020 · 0 comments
Labels
reactivity The Pluto programming paradigm

Comments

@fonsp
Copy link
Owner

fonsp commented Aug 12, 2020

eval and include both produce confusing behaviour. I don't think they can be easily fixed without a major rewrite, but the alternatives are relatively painless!

The alternative to eval(expr) is Core.eval(Main, expr) or better yet:

🏠 = Module()
Core.eval(🏠, expr)

because this avoids an implicit state in most cases.

The alternative to include(path) is still WIP, but it will look like #115 (comment)


Deprecating these two essentially means that your code is running in a baremodule (with using Base) instead of a module. Coincidence?

@fonsp fonsp added this to the 🛶 v0.13 milestone Aug 12, 2020
@fonsp fonsp added the reactivity The Pluto programming paradigm label Sep 9, 2020
@fonsp fonsp removed this from the 🛶 v0.13 milestone Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reactivity The Pluto programming paradigm
Projects
None yet
Development

No branches or pull requests

1 participant