Breaking API features and refactoring for 0.8 #427
No reviewers
Labels
No labels
breaking
bug
dependencies
good first issue
help wanted
unstable
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-uuid-rs/uuid!427
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/api-cleanup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm submitting a(n) (|feature|refactor|)
Description
Modules and Errors
This PR is a broad refactoring of our error types and module layout. The general pattern I've gone for is:
Error. All methods return this singleErrortype so it's easier for consumers to carryuuid::Errors in their own code.It'll also include some implementations for open PRs as we've been discussing. I imagine we'll want to spend time working through these changes :)
I've hidden our
preludemodule for now, because I'm not sure it's something we'll want to stabilize with (it's only got a few bits in it afterall).128bit support
Re-enables support for 128-bit numbers in the form of constructors on
Uuid, following the pattern that method names without an endian suffix are BE.No-std
Refactors our
no-stdsupport so we always mark the crate asno-stdso our std imports are always the same. This simplifies our std/core support so we need fewer modules.Timestamps
Includes the design proposed in #405 for timestamp support originally implemented by @jonathanstrong.
Related Issue(s)
Related PR(s)
Since this is a pretty big PR I'm trying to keep the individual commits clean so it should be easier to follow along.
This TODO bot is a bit of a nuisance...
(about the todo bot)
I think we should keep until 1.0, at which point we just remove it. The reason to keep it until then so that we have no overlooked bits. I am ok with the currently deleted comments from the bot
Also @KodrAus this is still a WIP right?
@kinggoesgaming I think this is ready for a review now 👍
There’s definitely more docs work to do and we can consider how to expose richer info out of our errors but I don’t think that needs to block a review or possible merge.
bors r+
Build succeeded