Results for: "remove_const"

No documentation available
No documentation available
No documentation available
No documentation available
No documentation available
No documentation available

Returns the full name of this Gem (see ‘Gem::BasicSpecification#full_name`). Information about where the gem is installed is also included if not installed in the default GEM_HOME.

No documentation available
No documentation available

Scanning is intentionally conservative because we have no way of rolling back an aggressive block (at this time)

If a block was stopped for some trivial reason, (like an empty line) but the next line would have caused it to be balanced then we can check that condition and grab just one more line either up or down.

For example, below if we’re scanning up, line 2 might cause the scanning to stop. This is because empty lines might denote logical breaks where the user intended to chunk code which is a good place to stop and check validity. Unfortunately it also means we might have a “dangling” keyword or end.

1 def bark
2
3 end

If lines 2 and 3 are in the block, then when this method is run it would see it is unbalanced, but that acquiring line 1 would make it balanced, so that’s what it does.

No documentation available

Create a new MatchLastLineNode node.

Create a new OptionalKeywordParameterNode node.

Retrieve the value of one of the InterpolatedStringNodeFlags flags.

Add the –clear-sources option

Add the –update-sources option

No documentation available
No documentation available

foo => bar => baz

^^^^^^^^^^

“foo #@bar”

^^^^^

foo in bar ^^^^^^^^^^

-> { _1 + _2 } ^^^^^^^^^^^^^^

Ripper gives back the escaped string content but strips out the common leading whitespace. Prism gives back the unescaped string content and a location for the escaped string content. Unfortunately these don’t work well together, so here we need to re-derive the common leading whitespace.

No documentation available
No documentation available
Search took: 7ms  ·  Total Results: 5438