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 usage of parse_transforms #5762

Closed
josevalim opened this issue Feb 12, 2017 · 5 comments
Closed

Deprecate usage of parse_transforms #5762

josevalim opened this issue Feb 12, 2017 · 5 comments

Comments

@josevalim
Copy link
Member

Elixir supports Erlang parse transforms but if we want to eventually perform less compiler steps and even compile directly to core one day, we will no longer be able to support those.

@michalmuskala
Copy link
Member

michalmuskala commented Feb 12, 2017

If this is going to happen, we need good alternatives. The only two places, I've used parse transforms were to make :dbg.fun2ms/1 or :ets.fun2ms/1 work. If there are convenient alternatives for those two use cases, I see no downsides in going forward with this change.

@fishcakez
Copy link
Member

fishcakez commented Feb 12, 2017 via email

@josevalim
Copy link
Member Author

@michalmuskala this may be a good starting point: https://github.com/ericmj/ex2ms

@holsee
Copy link

holsee commented Mar 16, 2017

What do you folks think this will mean for elixir projects which use things like Erlang's lager library which leverages parse transforms to remove logging levels that are not desired for a given build type?

I am working on erlang-lager/lager#348 "Add docs about using lager in elixir" and that is how I stubbled upon this issue. I don't want to be recommending an approach that would not be supported in the near future.

@josevalim
Copy link
Member Author

josevalim commented Mar 17, 2017 via email

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

No branches or pull requests

4 participants