-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sp-std -> core #3199
sp-std -> core #3199
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am glad we are doing this step by step.
As noted in #2101, I am not super convinced that the whole deprecation is a winning tradeoff, but I am too late to that conversation 🎩
There is merit in just doing all the core references (there are a lot of |
ok that set of changes looks good to me. |
bc2e5e1
First in a series of PRs that reduces our use of sp-std with a view to deprecating it. This is just looking at /substrate and moving some of the references from `sp-std` to `core`. These particular changes should be uncontroversial. Where macros are used `::core` should be used to remove any ambiguity. part of paritytech#2101
First in a series of PRs that reduces our use of sp-std with a view to deprecating it.
This is just looking at /substrate and moving some of the references from
sp-std
tocore
.These particular changes should be uncontroversial.
Where macros are used
::core
should be used to remove any ambiguity.part of #2101