Renaming the upcoming global import file to std.experimental.all #6186
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.
I just tried to explain this to someone as he was confused by
scripting
.scripting
was used because it was the first name suggested by @andralex, but while I don't hope that this will stay inexperimental
for too long, it's probably a good idea to useall
is it will immediately tell every reader what's going on.scripting
is rather vague.Credits: this has been suggested by @carun here #5916 (comment)
I know the name doesn't matter too much and we ideally can use
import std
soon, but it was a quick five minute change and will hopefully lead to less confusion.See also: #5916 (PR that introduced
std.experimental.scripting
)