> If I'm understanding you correctly, then what you would like for source_range for the example for foo and bar methods is then: I don't claim to have any suggestion for HERE docs because of the disjoint problem you mentioned. But cle...headius (Charles Nutter)
> The only choice for Prism.find there is to return the ForNode `for` syntax does not parse as a ForNode without the block, so the two are not separable. Calls do parse without the block and remain CallNode. A block is an argument to ...headius (Charles Nutter)
> The example of define_method(:foo) { ... } was given define_method is just a method call like any other. It should not be included in the range for the syntactic construct that is the block. What about do..end with a huge piece of c...headius (Charles Nutter)
byroot (Jean Boussier) wrote in #note-8: > I suspect removing that limitation wouldn't prevent JITs from optimizing the overwhelming majority of `rescue` statements as they'd still only list one of a few classes. Well, it wouldn't be...headius (Charles Nutter)
Eregon (Benoit Daloze) wrote in #note-7: > For the start position I think either is fine. > ... The `proc` part is irrelevant to the source of the block, and is only a method call receiver for a block argument. We wouldn't include any ...headius (Charles Nutter)
I think the better fix would be to reject literal types that are clearly not going to match. Ideally, the only cases that should be admitted to a rescue would be constant accesses, or other expressions that could potentially resolve a ty...headius (Charles Nutter)
matz (Yukihiro Matsumoto) wrote in #note-4: > `Ractor.make_shareable` does more than deep freezing and exists for Ractor. Its presence does not by itself justify `deep_freeze` in core. But deep freezing is the most visible effect, an...headius (Charles Nutter)
This path avoids the sources getting wiped out during `mvn clean`, since they are not generated during the maven build. This patch also moves the generated WASM build under src/main/wasm since it is really a source file and not a test f...headius (Charles Nutter)
* The Loader API lives under java/api. * The current native endpoint for the Prism shared library lives under java/native. * The WASM build and binding lives under java/wasm. The libraries will be released together but can be develope...headius (Charles Nutter)
This uses the JRuby rake-maven-plugin to generate the templates as part of the Maven build. The generated output for the Java templates will be under java/api/target/generated-sources/java. https://github.com/ruby/prism/commit/b257151391headius (Charles Nutter)