Results for: "fnmatch"

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

Load extra data embed into binary format String object.

No documentation available
No documentation available

Adds this spec’s require paths to LOAD_PATH, in the proper location.

Reset nil attributes to their default values to make the spec valid

No documentation available
No documentation available

Processes the topmost available {RequirementState} on the stack @return [void]

@return [ResolutionState] the state whose ‘requirement` is the given

`requirement`.
No documentation available

In case we’re building docs in a background process, this method waits for that process to exit (or if it’s already been reaped, or never happened, swallows the Errno::ECHILD error).

No documentation available

@return [Integer] The index to which the resolution should unwind in the

case of conflict.

Attempts to swp the current {#possibility} with the already-activated spec with the given name @return [Boolean] Whether the possibility was swapped into {#activated}

Pushes a new {DependencyState} that encapsulates both existing and new requirements @param [Array] new_requirements @return [void]

No documentation available
No documentation available

Pushes a new {DependencyState}. If the {#specification_provider} says to {SpecificationProvider#allow_missing?} that particular requirement, and there are no possibilities for that requirement, then ‘state` is not pushed, and the node in {#activated} is removed, and we continue resolving the remaining requirements. @param [DependencyState] state @return [void]

Search took: 3ms  ·  Total Results: 2025