There is not a prevention to parse both formats but also there is not a reason to have 2 formats.
Currently to handle the warnings and errors anyone who want to do that have to create 2 regex to handle each one, with one format you only need one. I think there is not a problem if we normalize that.I'm facing that problem in Github Actions in this pull request: https://github.com/actions/setup-elixir/pull/11 And i will be glad to make a collaboration in the core of elixir if you all allow me to do so. El mié., 27 de nov. de 2019 a la(s) 02:59, Louis Pilfold (lo...@lpil.uk) escribió: > Hello! > > What prevents the tool from attempting to parse both formats and using > whichever succeeds? That way this feature can exist without any changes to > the compiler. > > Cheers, > Louis > > On Wed, 27 Nov 2019, 06:11 Mijail Rondon, <mijail.ron...@gmail.com> wrote: > >> I think i can make the change for that. >> >> Is on lib/elixir/src/elixir_errors.erl >> >> El miércoles, 27 de noviembre de 2019, 0:57:00 (UTC-5), Mijail Rondon >> escribió: >>> >>> Hello Elixir Core, >>> >>> Currently we have different ways to display errors or warnings during >>> compile time, we should normalize the output. >>> >>> For example, warnings are displayed as: >>> >>> warning: unused alias Stream >>> lib/actions_sample.ex:2 >>> >>> and compile errors as: >>> >>> ** (SyntaxError) lib/actions_sample.ex:15: unexpectedly reached end of >>> line. ... >>> >>> So, no problem with compile errors but warnings should have the same >>> format as: >>> >>> ** (Warning) lib/actions_sample.ex:2: unused alias Stream >>> >>> The main reason to make this change is because in CI we have the ability >>> of catch those warnings or errors >>> and add annotations on specific lines of the corresponding files. >>> >>> If we normalize the warnings this will be possible to add annotations of >>> warnings to. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "elixir-lang-core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elixir-lang-core+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elixir-lang-core/491c2a71-560e-4df3-9547-98696502aaf8%40googlegroups.com >> <https://groups.google.com/d/msgid/elixir-lang-core/491c2a71-560e-4df3-9547-98696502aaf8%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elixir-lang-core+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CABu8xFDk7_z2WoqBCMAOFjNpe3kCFoQC0M0%2BkV%2BwrA4sGtttPg%40mail.gmail.com > <https://groups.google.com/d/msgid/elixir-lang-core/CABu8xFDk7_z2WoqBCMAOFjNpe3kCFoQC0M0%2BkV%2BwrA4sGtttPg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAJ_DNyX3yPy043RsBbBKx9j-_m8B4OaofovN4dMY23gKEYj2QQ%40mail.gmail.com.
