Results for: "strip"

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
No documentation available
No documentation available
No documentation available

@return [Object] most up-to-date dependency in the possibility set

Creates and pushes the initial state for the resolution, based upon the {#requested} dependencies @return [void]

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

`requirement`.

@param [Object] requirement @return [Array<Object>] the list of requirements that led to

`requirement` being required.
No documentation available

Raises a VersionConflict error, or any underlying error, if there is no current state @return [void]

@param [String] name @return [Object] the requirement that led to a version of a possibility

with the given name being activated.

Requires the dependencies that the recently activated spec has @param [Object] possibility_set the PossibilitySet that has just been

activated

@return [void]

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

@return [Integer] index of state requirement in reversed requirement tree

(the conflicting requirement itself will be at position 0)

@return [Boolean] where the requirement of the state we’re unwinding

to directly caused the conflict. Note: in this case, it is
impossible for the state we're unwinding to to be a parent of
any of the other conflicting requirements (or we would have
circularity)

Filter’s a state’s possibilities to remove any that would not satisfy the requirements in the conflict we’ve just rewound from @param [UnwindDetails] unwind_details details of the conflict just unwound from @return [void]

Attempts to update the existing vertex’s ‘PossibilitySet` with a filtered version @return [void]

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 vertex in {#activated} is removed, and we continue resolving the remaining requirements. @param [DependencyState] state @return [void]

Search took: 5ms  ·  Total Results: 1474