You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a debug_info_key is used; if Gradualizer relies on the BEAM files (rather than on the source files), I would have expected that an option existed to specify that key (unless ~/.erlang.crypt is used?)
Thanks in advance for any hint,
Olivier.
[1] BTW, if we update a Gradualizer clone and just run make escript, a new escript is indeed generated but it does not rely on the recently pulled module sources that shoud be recompiled: instead of reporting v0.3.0-9-g81385f6 it was for example still v0.2.0-162-g182be65 (but apparently make clean escript does the job).
The text was updated successfully, but these errors were encountered:
Hi,
Using latest Gradualizer version [1], the following command reports a type, text/0, presumably in ui_test.erl:
However https://github.com/Olivier-Boudeville/Ceylan-Myriad/blob/713c7440750c0bc2d36fcdd909ac2cad40830f46/test/user-interface/ui_test.erl#L62 shows that there is no such type used there (or even referenced in that source file).
If it is relevant:
Thanks in advance for any hint,
Olivier.
[1] BTW, if we update a Gradualizer clone and just run
make escript
, a new escript is indeed generated but it does not rely on the recently pulled module sources that shoud be recompiled: instead of reporting v0.3.0-9-g81385f6 it was for example still v0.2.0-162-g182be65 (but apparentlymake clean escript
does the job).The text was updated successfully, but these errors were encountered: