![]() This required changing IntRange resolvedFinalArit圜hange() to ArityInterval resolvedFinalArityInterval() on all Calls, which was a large change. Any call to unquote_splicing(.) can end up have 0 to infinite parameters, so it means when one is seen, the range of minimum.maximum should change to an open interval of minimum. Need to have their arity not be the number of PsiElements in the parentheses. ![]() KeepProcessing & match.whileInStabBod圜hildExpressions <- clauses do def _schema_ ( unquote_splicing ( args ) ), do : unquote ( body ) end While preparing 11.11.0, I had to add a fix: // descend in modular to check for nested modulars in case their relative name is being used ![]() Using Yacto as a test project, I ran the Elixir References Inspection over the whole project and manually checked any errors to see if I could make the resolution better. It has reproduction steps and an open source repository I can use to run those steps the same as the reporter. It was in #1997 where Tomoki Odaka gave a specific file in gumi/yacto to reproduce the StackOverflowError bugs.īy the way, this is an excellent bug report. It was the next two bugs that shaped the focus of 11.12.0. That bug was perennial class of “read access is allowed from event dispatch thread”, which is fairly easy to fix with a readAction. Within an hour of releasing 11.11.0, Tomoki Odaka had already opened a bug. IntelliJ Elixir, the Elixir plugin for JetBrains IDEs (IntelliJ IDEA, RubyMine, WebStorm, etc), version 11.12.0 has been released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |