From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] fix ref822
Date: Fri, 22 Nov 2019 22:14:25 +0100 [thread overview]
Message-ID: <BD20254A4D44CDBA3E45CBF7D9595D10@felloff.net> (raw)
In-Reply-To: 663176CA83C9DF3BA009A5067FE7C47A@eigenstate.org
what do you mean with "different results"? what do i miss? i was
thinking that as we deduplicate the end result anyway, the only
difference would be that we retain more unique values in the case
of duplicates. but i might be missing something. the assumption was
that Nref was an arbitrary choosen value and the differences only
kick in when we reach that number of refernces in the array.
old code:
a = uniq(trunc-left(cat(a, uniq(trunc-right(tokenize(f))))))
new code:
a = trunc-left(uniq(cat(a, trunc-right(tokenize(f)))))
you can see that when there are no duplicates, that is, when
you remove the uniq() functions, they'r both identical
expressions.
--
cinap
next reply other threads:[~2019-11-22 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 21:14 cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-22 21:24 ori
2019-11-22 18:39 ori
2019-11-22 17:59 ori
2019-11-22 7:21 cinap_lenrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD20254A4D44CDBA3E45CBF7D9595D10@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).