refactor(map): deprecate op-get for future migration #2017
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.
In the future, we will have
op_get
returnV
instead ofV?
andget
returnV?
.For other functions, if there are a 'unsafe' implementation and a 'safe', the unsafe one will be named as
unsafe_xxx
. Otherwise it will just named as it is.cc @Yoorkin the
json.mbt
emitted two same warnings