Skip to content

Conversation

@cgay
Copy link
Member

@cgay cgay commented Aug 6, 2023

Incompatible change for lowercase? and uppercase?

cgay added 4 commits August 6, 2023 00:22
This is a backwards-incompatible change and will be followed by a commit to
increment the major version of the strings package.

It's unintuitive for `lowercase?('8')` to return `#t` since being lowercase
implies being alphabetic, and similarly for `uppercase?`. So this change makes
both `lowercase?('8')` and `uppercase?('8')` return `#f`.

What exactly `lowercase?("f8")` should mean is less clear, but as a member of
the generic function it should match the method on `<character>` which, I
believe, implies that it should be equivalent to `every?(lowercase?, string)`.
Because the implementation is trivial and because I can't think of a common use
case for this method, I'm removing it entirely and making this a non-generic
function.
This works better with the Furo theme.
@cgay cgay merged commit dccd106 into dylan-lang:master Aug 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants