Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This currently has issues due to rust-lang/rust#50822. Event fairly mundane examples will not compile because the compiler does not infer the default parameter without a type annotation, and type namespace paths are not type annotations.
The following example...
...fails with...
I'm undecided about what approach to use to solve this. Perhaps we should use a series of type aliases within the crate to specify a default
Spin
relax strategy, thereby avoiding major breakage for most users but allowing advanced users to opt-in, albeit through a more unconventional way of accessing the types?