Results for: "pstore"

def foo(bar); end

^^^

def foo(*bar); end

^^^^

def foo(*); end

^

A shareable constant.

Visit a heredoc node that is representing a string.

Visit a heredoc node that is representing an xstring.

Returns the octet string representation of the elliptic curve point.

conversion_form specifies how the point is converted. Possible values are:

• :compressed

• :uncompressed

• :hybrid

def foo((bar, baz)); end

^^^^^^^^^^

Foo::Bar += baz ^^^^^^^^^^^^^^^

@foo += bar ^^^^^^^^^^^

Foo::Bar += baz ^^^^^^^^^^^^^^^

@foo += bar ^^^^^^^^^^^

@@foo += bar

becomes

@@foo = @@foo + bar

$foo += bar

becomes

$foo = $foo + bar

@foo ||= bar

becomes

@foo || @foo = bar

foo += bar

becomes

foo = foo + bar

The logical inverse of ‘capture_last_end_same_indent`

When there is an invalid block with an ‘end` missing a keyword right after another `end`, it is unclear where which end is missing the keyword.

Take this example:

class Dog       # 1
    puts "woof" # 2
  end           # 3
end             # 4

the problem line will be identified as:

> end            # 4

This happens because lines 1, 2, and 3 are technically valid code and are expanded first, deemed valid, and hidden. We need to un-hide the matching keyword on line 1. Also work backwards and if there’s a mis-matched end, show it too

Returns tokens corresponding to the location of the node. Returns nil if keep_tokens is not enabled when parse method is called.

root = RubyVM::AbstractSyntaxTree.parse("x = 1 + 2", keep_tokens: true)
root.tokens # => [[0, :tIDENTIFIER, "x", [1, 0, 1, 1]], [1, :tSP, " ", [1, 1, 1, 2]], ...]
root.tokens.map{_1[2]}.join # => "x = 1 + 2"

Token is an array of:

• id

• token type

• source code text

• location [ first_lineno, first_column, last_lineno, last_column ]

Returns AST nodes under this one. Each kind of node has different children, depending on what kind of node it is.

The returned array may contain other nodes or nil.

Serializes the DH parameters to a PEM-encoding.

Note that any existing per-session public/private keys will not get encoded, just the Diffie-Hellman parameters will be encoded.

PEM-encoded parameters will look like:

-----BEGIN DH PARAMETERS-----
[...]
-----END DH PARAMETERS-----

See also public_to_pem (X.509 SubjectPublicKeyInfo) and private_to_pem (PKCS #8 PrivateKeyInfo or EncryptedPrivateKeyInfo) for serialization with the private or public key components.

Serializes the DH parameters to a PEM-encoding.

Note that any existing per-session public/private keys will not get encoded, just the Diffie-Hellman parameters will be encoded.

PEM-encoded parameters will look like:

-----BEGIN DH PARAMETERS-----
[...]
-----END DH PARAMETERS-----

See also public_to_pem (X.509 SubjectPublicKeyInfo) and private_to_pem (PKCS #8 PrivateKeyInfo or EncryptedPrivateKeyInfo) for serialization with the private or public key components.