Jesper Eskilson
Jesper Eskilson
With latest gradualizer version (today's master), the error is different ```erlang Error: {noproc,{gen_server,call,[gradualizer_db,{get_spec,lists,map,2},5000]}} [{gen_server,call,3,[{file,"gen_server.erl"},{line,247}]}, {typechecker,type_check_fun,3, [{file,"/home/jespereskilson/dev/aoc_erlang/_build/default/plugins/gradualizer/src/typechecker.erl"}, {line,3025}]}, {typechecker,do_type_check_expr,2, [{file,"/home/jespereskilson/dev/aoc_erlang/_build/default/plugins/gradualizer/src/typechecker.erl"}, {line,1547}]}, {typechecker,type_check_expr,2, [{file,"/home/jespereskilson/dev/aoc_erlang/_build/default/plugins/gradualizer/src/typechecker.erl"}, {line,1425}]}, {typechecker,infer_clause,2, [{file,"/home/jespereskilson/dev/aoc_erlang/_build/default/plugins/gradualizer/src/typechecker.erl"}, {line,3267}]}, {lists,map,2,[{file,"lists.erl"},{line,1243}]}, {typechecker,infer_clauses,2, [{file,"/home/jespereskilson/dev/aoc_erlang/_build/default/plugins/gradualizer/src/typechecker.erl"}, {line,3247}]},...
What is the status of this now? I have some minor improvements to `rebar.config.script` and `yaws.app.src.script` (avoid regenerating files unless they have changed).
This is using this branch: https://github.com/erszcz/Gradualizer/tree/record-union-with-any
The actual source code is parenthesized correctly: ```erlang %% @doc Encode URI into a percent-encoding string. -spec encode_uri(list() | binary()) -> binary(). encode_uri(Value) when is_list(Value) -> encode_uri(list_to_binary(Value)); encode_uri(Value) when is_binary(Value)...
I can report a bug, but I'm a bit unsure how to create a reproducible example without involving Gradualizer.
> You need to make handle_crash/2 take the extra St argument and also pass it along to a user defined crashmsg/4 instead of the existing crashmsg/3. > > Furthermore, you...
> Yeah... Once again... It's because of _macros_ cry. > > I'm sorry, but katana-code / erl_syntax can't parse that code. I'd like to use this on our code base,...
Isn't it at least possible to have the parser tell you if it was able to parse the file, and if not just ignore the entire file? I was hoping...
This was an incomplete application of an internal patch of ours, and it is indeed not backwards compatible with existing crashmsg/3 implementations. We have `handle_crash/3` defined in `yaws_server.erl` as ```erlang...