You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that when using /SKIP, only the first record is tested for uniqueness.
>>a: [1234561234]
== [1234561234]
>>unique/skip a 2== [12345634] ; should be [1 2 3 4 5 6]>>a: [123456123456]
== [123456123456]
>>unique/skip a 2== [1234563456] ; should be [1 2 3 4 5 6]>>unique/skip a 3== [123456456] ; should be [1 2 3 4 5 6]
Submitted by: henrikmk
It appears that when using /SKIP, only the first record is tested for uniqueness.
Imported from: CureCode [ Version: alpha 49 Type: Bug Platform: All Category: Native Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#726
Comments:
Submitted by: henrikmk
This bug appears also in R2, it seems: http://www.rebol.net/cgi-bin/rambo.r?id=4018&
Submitted by: BrianH
This is a general problem with the functions which use /skip for dealing with series of fixed records. We're discussing the issue in #428.
The text was updated successfully, but these errors were encountered: