Raised when the buffer cannot be allocated for some reason, or you try to use a buffer that’s not allocated.
Raised when the query given to a pattern is either invalid Ruby syntax or is using syntax that we don’t yet support.
Specifies a Specification object that should be activated. Also contains a dependency that was used to introduce this activation.
A VendorSpecification represents a gem that has been unpacked into a project and is being loaded through a gem dependencies file through the path: option.
Gem::Security default exception type
RubyVM::AbstractSyntaxTree::Location instances are created by RubyVM::AbstractSyntaxTree::Node#locations.
This class is MRI specific.
SSLServer represents a TCP/IP server socket with Secure Sockets Layer.
An OpenSSL::OCSP::SingleResponse represents an OCSP SingleResponse structure, which contains the basic information of the status of the certificate.
An error class raised when missing nodes are found while computing a constant path’s full name. For example:
-> raises because the constant path is missing the last part
A location field represents the location of some part of the node in the source code. For example, the location of a keyword or an operator. It resolves to a Prism::Location in Ruby.
A field representing the start and end character offsets.
Represents a specification retrieved via the rubygems.org API.
This is used to avoid loading the full Specification object when all we need is the name, version, and dependencies.
A GitSpecification represents a gem that is sourced from a git repository and is being loaded through a gem dependencies file through the git: option.
Represents a possible Specification object returned from IndexSet. Used to delay needed to download full Specification objects when only the name and version are needed.
An InstalledSpecification represents a gem that is already installed locally.
A set of gems for installation sourced from remote sources and local .gem files
A LocalSpecification comes from a .gem file on the local filesystem.
The LockSpecification comes from a lockfile (Gem::RequestSet::Lockfile).
A LockSpecification’s dependency information is pre-filled from the lockfile.
The Resolver::SpecSpecification contains common functionality for Resolver specifications that are backed by a Gem::Specification.