Eksperimental
Eksperimental
@marianoguerra there are a few more issues, but I will see if they are fixed once these last two bugs are covered. I will submit them if they are not.
A good compromise would be to remove the underscore if there is no other variable named like that. If there is, leave it and let the user deal with the...
I see what you mean. It is related to the other variable scope issue. It could use the name of another variable defined outside `case`, or the program relies on...
Should we emit a warning at transpilation time? So the user knows there's something wrong with his/her code?
I see. Is it possible to switch, or a whole revamp would be needed?
> We cannot guarantee that code that we expand in one node for Elixir v1.18 will work on v1.17 or vice-versa. There were actually issues in the past, hence the...
> @eksperimental do you need any help with this one? Hi @yordis. The PR is a proof of concept. As it is now it's OK. There's another PR going on...
There's one thing that is left. The error message says the docs failed to build due to warnings, which is not true. The docs are generated: I think docs should...
> We should definitely produce a build, because it allows users to introspect what was rendered even in the presence of warnings. Great. That simplifies things. There's is one issue...
> Producing at least 1 build is fine. I believe it would be easier to inspect the HTML version first anyways. You could also specify which format you wanted if...