World: r3wp

Nope.

Now that I have internet again (it's been out for possibly a week) 
I'll check with Carl about this, but I remember code from 2007-2008 
that depended on this change, even from before SELECT was extended 
to objects and maps. It's used to make blocks that look like spec 
blocks for objects or maps act like objects or maps. SELECT does 
EQUAL? comparison, and SELECT/case does STRICT-EQUAL? comparison. 
So you can make it work by using SELECT/case. Note: Words now support 
case-sensitivity in blocks too, letting them be searched with FIND/case 
and SELECT/case.

>> select [a 1 :a 2] quote :a
== 1
>> select/case [a 1 :a 2] quote :a
== 2

fine!

I'll add this info to the ticket in a comment and dismiss it. It's 
actually more powerful than R2 :)

but not perfect as the case-sensitivity may cause problems...but 
I can live with it.

but not perfect as the case-sensitivity may cause problems...but 
I can live with it.

Not when you realize that this is consistent throughout R3, and just 
don't mix case when you don't need to.

The trick is that objects and maps are case-preserving rather than 
case-sensitive, so their fields get the same case as the first instance 
of the word. Plus, case-insensitivity is a little broken for a lot 
of languages right now (Unicode case is a complex problem).

Characters are case-sensitive

 is a pretty misleading description of the difference you've pointed 
 out between SELECT and SELECT/CASE, Brian. 


I would appriciate SELECT/STRICT over /CASE, /STRICT would even be 
usefull to imply case sensitivity, at least it seems better suited 
to express the semantic difference between the refined und the unrefined 
function call .

Same for 

>> find/case [a :a] quote :a
== [:a]
>> replace/case [a :a] quote :a quote a:
== [a a:]
>> alter/case [a] [:a]
== true


DIFFERENCE, UNIQUE and other "set-functions" obviously haven't been 
subject to change when the treatment of blocks, objects and maps 
converged:

>> difference/case [:a] [a:] 
== []
>> unique/case [a: a :a] 
== [a:]
>> union/case [a] [:a] 
== [a]
>> intersect/case [a] [:a] 
== [a]
>> exclude/case [a] [:a]
== []


In all cases, /STRICT would read at least as well as /CASE, if not 
better.

Christian, please report the latter cases as bug.

I'm not sure if it isn't by design, at least I wouldn't be surprised 
if being told so. Anyways, I'd prefer it being a bug, so, added it 
to CureCode.

Given the above discussed behaviour, I would very much prefer /STRICT 
instead of /CASE as well. But I fear the chance for such thorough 
naming improvements has long passed.

hmm, you should post it as a separate CC item (wish?)

yes, using /CASE for strict word comparison is VERY ugly. the only 
reason I can think of is that Carl didn't want to add a refinement 
just for this.

Well, if there's sufficient backing in the community, we really should 
manifest that in the form of a CC wish.

No problem with me

I'd bet /CASE is not used that much for word comparison in the R3 
mezz code.

(if at all, maybe in r3gui)

do not think so

Already did (curecode that wish above).

#1832

already added my weight behind the /STRICT naming  :-)

The /strict option sounds interesting, and would solve those inconsistencies. 
However, it would need to be an additional option; /case would need 
to remain for compatibility reasons.

I'm not sure it's completely OK though, since there is one part of 
strict comparison that SELECT/case doesn't cover: binding.
>> select/case reduce [use [a] ['a] 1 'a 2] 'a
== 1
>> strict-equal? use [a] ['a] 'a
== false

Nor do we want it to, because SELECT, FIND and other functions to 
which /strict would apply would generally not be applied to data 
which could be guaranteed to have the same binding as the value you 
are searching for.

Christian, REPLACE and ALTER are mezzanines that call FIND. You don't 
need to include them in the examples.

A new refinement for considering datatypes would be a good idea (if 
a bit overhead-inducing), but probably not the name /strict. We have 
to keep the /case refinement because of the legacy naming rules, 
but those don't prohibit adding new refinements.

The #1832 ticket needs its summary line changed accordingly.

select/a-bit-more-than-case-but-a-bit-less-than-strict-but-definitely-not-equiv-or-same

We can't remove /case. So the new option would not have to be a superset 
of /case, it would be additive. What would you call an option that 
made it consider datatypes? Keep in mind that this option would only 
apply to block types, so would be overhead for other types that implement 
the FIND and SELECT actions.

If we can neither remove nor superset /case, it is hardly worth talking 
about this at all.

If we called the option /type then /case would check case, /type 
would check types, and /case/type would check both. That is what 
I meant by additive.

Understood. And for me that's hardly worth talking about.

Instead of inflicting the pain of having to type /case/type just 
leaving the current /case behaviour as-is and updating the doc strikes 
me as more sensible.

I'm OK with having the current behavior of FIND and SELECT, and extending 
it to the set functions. But if others have problems with that and 
want /case to just be case, then we may need the extra option. All 
of this is really a complaint about #1830 being dismissed.

Orthogonal issues.

Or alternative solutions, rather.

Checking SELECT, it's clear that its behavior is not consistent among 
different classes of value types either. The simplest solution would 
be to change #1830 into something that can be undismissed, and then 
dismiss #1831 and #1832.

That means expanding the complaint of #1830 and giving it a different 
justification.

Since you are the one who dismissed it in the first place, feel free 
to go ahead and do as you deem right.

Depending on how #1830 is resolved, #1831 and #1832 will either need 
to be dismissed or rewritten. I'm going to have to defer them until 
#1830 is decided upon.

Done. Check out the new http://issue.cc/r3/1830for the whole issue.

pulled myweight.

I do not want to use the "immediate value" notion, since it is an 
"implementation detail" in the sense, thant e.g. Doc's attempt implementation, 
while attempting to be compatible, has drawn the line differently.

And, if done properly, you would not be able to discern

So if the new-line attribute is immutable, is that observable?

Yes, the immutability *is*

And would that mean that calling the new-line function creates a 
new copy of the value, toggles the new-line bit, and places that 
new value in the appropriate slot?

I may not follow what you are after, but is a sign of integers immutable, 
and is that (according to your opinion) observable?