Re: [elixir-core:11718] Code.eval_string() raises warnings when parsing Mix.lock

2024-03-21 Thread Thibaut Barrère
Thanks Wojtek - I was unsure if this would result in a potential change request (on the format of Mix.lock itself), hence my posting here, but well noted! Thanks for hint as well, that should do! -- Thibaut Le jeudi 21 mars 2024 à 17:14:18 UTC+1, woj...@wojtekmach.pl a écrit : > Please use

Re: [elixir-core:11716] Code.eval_string() raises warnings when parsing Mix.lock

2024-03-21 Thread Wojtek Mach
Please use ElixirForum and such to ask questions as broader community can answer as well as see replies. This ML tends to be focus on feature requests. On v1.16 you should be able to pass emit_warnings: false. I believe there are equivalents on prior versions, they should be documented in this

[elixir-core:11716] Code.eval_string() raises warnings when parsing Mix.lock

2024-03-21 Thread Thibaut Barrère
Hello! A slightly exotic use-case, but I would like to have your opinion :-) While doing maintenance work, I often leverage the fact that Mix.lock content is "valid Elixir" to implement useful stuff. Two examples are: -