Results for: "remove_const"

No documentation available

Checks if this specification meets the requirement of dependency.

Invoked by any method that performs a non-reverse DNS lookup. The most notable method is Addrinfo.getaddrinfo, but there are many other.

The method is expected to return an array of strings corresponding to ip addresses the hostname is resolved to, or nil if it can not be resolved.

Fairly exhaustive list of all possible call-sites:

Clear recorded tracing information.

Create parser string nodes from a single prism node. The parser gem “glues” strings together when a line continuation is encountered.

No documentation available

Waits up to the continue timeout for a response from the server provided we’re speaking HTTP 1.1 and are expecting a 100-continue response.

Returns the column number in code units for the given encoding for the given byte offset.

Specialized version of ‘code_units_column` that does not depend on `code_units_offset`, which is a more expensive operation. This is essentially the same as `Prism::Source#column`.

The column number in characters where this location ends from the start of the line.

in “” in “foo”

No documentation available
No documentation available

The name of the configuration file.

No documentation available
No documentation available

Extracts S3 configuration for S3 bucket

Returns URL-escaped string following RFC 3986.

Returns URL-unescaped string following RFC 3986.

No documentation available
No documentation available

Sets the value of field 'Content-Type'; returns the new value; see Content-Type request header:

req = Net::HTTP::Get.new(uri)
req.set_content_type('application/json') # => ["application/json"]

Net::HTTPHeader#content_type= is an alias for Net::HTTPHeader#set_content_type.

No documentation available

Marshal dumps exit locations to the given filename.

Usage:

If --yjit-exit-locations is passed, a file named “yjit_exit_locations.dump” will automatically be generated.

If you want to collect traces manually, call dump_exit_locations directly.

Note that calling this in a script will generate stats after the dump is created, so the stats data may include exits from the dump itself.

In a script call:

at_exit do
  RubyVM::YJIT.dump_exit_locations("my_file.dump")
end

Then run the file with the following options:

ruby --yjit --yjit-trace-exits test.rb

Once the code is done running, use Stackprof to read the dump file. See Stackprof documentation for options.

Fetch the start code units column of the value, for the encoding that was configured on the repository.

Search took: 5ms  ·  Total Results: 3316