[#107867] Fwd: [ruby-cvs:91197] 8f59482f5d (master): add some tests for Unicode Version 14.0.0 — Martin J. Dürst <duerst@...>
To everybody taking care of continuous integration:
3 messages
2022/03/13
[#108090] [Ruby master Bug#18666] No rule to make target 'yaml/yaml.h', needed by 'api.o' — duerst <noreply@...>
Issue #18666 has been reported by duerst (Martin D端rst).
7 messages
2022/03/28
[#108117] [Ruby master Feature#18668] Merge `io-nonblock` gems into core — "Eregon (Benoit Daloze)" <noreply@...>
Issue #18668 has been reported by Eregon (Benoit Daloze).
22 messages
2022/03/30
[ruby-core:107961] [Ruby master Feature#18642] Named ripper fields
From:
"kddeisz (Kevin Newton)" <noreply@...>
Date:
2022-03-17 21:36:24 UTC
List:
ruby-core #107961
Issue #18642 has been reported by kddeisz (Kevin Newton). ---------------------------------------- Feature #18642: Named ripper fields https://bugs.ruby-lang.org/issues/18642 * Author: kddeisz (Kevin Newton) * Status: Open * Priority: Normal ---------------------------------------- One of the biggest pain-points working with the existing ripper subclasses is that you have to know what each array index represents in any given node. I'm proposing adding a subclass of ripper where every field is named so that it makes it easier to work with different versions of ruby. The PR is here: https://github.com/ruby/ruby/pull/5679. Below is copied the description from the PR. This is a new subclass of the Ripper parser. It is based on/extracted from the work done in https://github.com/ruby-syntax-tree/syntax_tree. This subclass is similar to SexpBuilderPP in that it provides individual shapes per production rule from ripper. However, there are a couple of differences: * Tree uses class instances instead of arrays to represent nodes. * Comments are automatically attached to the various nodes when parsing is finished. * A couple of additional nodes are added for clarity (i.e., ArgStar, Not, PinnedBegin, etc.). * Every node has location information attached to it (as opposed to just the scanner event nodes). * There's a standard interface for descending the tree (child_nodes). * Additionally, each node has pattern matching (both array and hash patterns) as well as pretty_print defined to make it easier to work with. I think we should ship this with Ruby to make it easier to build tools (like formatters and linters) on top of this structure. It also will make it easier to change the parser in the future (if we ever do) because any tools built on top of these objects will not have to worry about the specific order of the nodes (unlike the SexpBuilderPP version) since everything has a named field. Additionally, since everything is written in pure Ruby, it makes it easy for other implementations of Ruby to benefit. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>