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
Str.match not documented / Str.subst does not list all options [some are inaccurate/incomplete] #919
Comments
|
this depends on lizmats match overhaul. At least the return type may change depending adverbs. |
|
Does lizmat plan to do any changes in this area now? Issue seems pretty old.
|
|
@zoffixznet, can you look at |
No, as I understand it, everything was finished off last year.
Briefly looking at this, I see the two original concerns are still valid:
And I spotted one more error: The second thing is it seems the accepted adverbs are scattered between regexes#Adverbs, match docs, and subst docs. For example But perhaps it makes more sense to document it all in just one place (in regexes#Adverbs). Most of the adverbs are the same in A few adverbs only make sense for matching (e.g. So to me it feels all of these can be neatly documented in one space and each include these three indicators (maybe an icon with |
|
The page on |
The Str.match method appears to undocumented. Moreover,
Str.substuses it for regex matching, and it appears that some of the options accepted byStr.matchare not listed forStr.subst(some may be applicable on forStr.subst-mutatethat returnsMatchobjects).Lastly, the
:nth(and aliases) also take aWhateverwhile:xdoes not take aCallable, but does takeRangeorWhateverThe text was updated successfully, but these errors were encountered: