-
Notifications
You must be signed in to change notification settings - Fork 36
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
RFC: Replace unibool with uniprop-bool in S15 #119
Comments
Nobody has commented yet, can anybody weigh in? @perl6/perl6 If no objections I would like to update the spec and add some tests into roast for this. |
To be honest, I'm not sure I understand what is going to happen after this change.
Can't we have something that is more consistent with the rest of the language? For example, |
Well, just All the different enumerated properties have mostly different values for codes without the property OR which have been explicitly specified as having that value.
|
The current spec says
uniprop
returns the narrowest numerical type for numerical properties and boolean for boolean properties, and returns Str for all other properties.It also mentions a
unibool
function. At the moment we haveuniprop-bool
,uniprop-int
,uniprop-str
in Rakudo, but they are not in the docs or Roast. I think the only useful one of these we might want to keep would be theuniprop-bool
function, which could be used to check the absence of a property.This code below shows an example I think makes logical sense, and is also currently what Rakudo does.
See discussion here:
https://irclog.perlgeek.de/perl6/2016-12-16#i_13751405
@jnthn
The text was updated successfully, but these errors were encountered: