junke

50 ms·

481.
by junke 10y ago
Not only is this allowed, it is encouraged. Why would people use sock-puppets, I don't know. It seems that the SO team has special ways to detect voting frauds.
482.
by junke 10y ago
Sure, in a perfect world the documentation would guess who I am and adapt accordingly, be both highly detailed when I need it or informal when I don't. But it's not a perfect world, I want to get stuff done. I have twenty years of
483.
by junke 10y ago
The "text blob" always starts explaining precisely what kind of return value to expect under which circumstances. The return value's type can change depending on the context, and using plain text is somewhat easier to write a
484.
by junke 10y ago
> You aren't putting yourself in the shoes of a beginner. How do you know if I am putting myself in the shoes of a beginner or not? And what kind of beginners are we talking about? Are they comfortable with a browser? Do they alread
485.
by junke 10y ago
> Now, compare that to what happens when I search for the same in Python. I get this: > https://docs.python.org/2/library/re.html I clicked and I saw the kind of technical documentation I love to read: preci
486.
by junke 10y ago
Languages are part of the ergonomics of code writing.
487.
by junke 10y ago
Or without OpenSSL (ql:quickload :isaac) ;; FIRST TIME (one of both) ;; using (random), which on sane implementations should rely on /dev/urandom (defvar *isaac* (isaac:init-common-lisp-random-seed)) ;; us
488.
by junke 10y ago
Reading this story, I was curious about ISAAC, so I posted a link to its webpage in another post ( https://news.ycombinator.com/item?id=12441451 ), hoping people would give their opinion on it. Do you have experience with ISA
489.
ISAAC: a fast cryptographic random number generator(burtleburtle.net)
3 points by junke 10y ago|0 comments
490.
by junke 10y ago
Then someone will update the XKCD comic with a similar smile on their face.
491.
by junke 10y ago
In my view this is more a question of simple interface vs. simple implementation. Having cross-references at the language level gives a uniform and simplified interface at the cost of more having to develop careful tools. Not saying refs&#x
492.
by junke 10y ago
Yet, a lot of hierarchical structures I see are full of "ref" and "id" attributes, which effectively encode cyclic graphs.
493.
by junke 10y ago
That's the case in practice (both the internal limits and the optimizations). For example Common Lisp's ARRAY-TOTAL-SIZE-LIMIT is a fixnum. The default numeric type is not bignum, however, the numeric tower is here to use them onl
494.
by junke 10y ago
()
495.
by junke 10y ago
Basic, Python 2, Perl print "Hello World"
496.
by junke 10y ago
See also https://codegolf.stackexchange.com/questions/tagged/polyglot
497.
by junke 10y ago
Both
498.
by junke 10y ago
Here is an example of an "unusual" case where the compiler can detect errors in statically known regexes. This fails at compilation with Opening paren has no matching closing paren. at position 0 in string "(ab"
499.
by junke 10y ago
That makes sense. Thanks.
500.
by junke 10y ago
See also: Is there a specific reason for the poor readability of regular expression syntax design? http://programmers.stackexchange.com/q/298564/33157
501.
by junke 10y ago
I like both Emacs and OCaml but I can't see a case where I would want to use Ecaml. In what situation is it useful?
502.
by junke 10y ago
I read it as: Someone unfollows you. Then what? Probably questioning the utility of the tool.
503.
by junke 10y ago
Isn't "color.Unset()" dead code? if err != nil { color.Set(color.FgRed, color.BlinkSlow) log.Fatal(err) color.Unset() } https://github.com/dlion/go-odbye/blob/master/mai
504.
by junke 10y ago
There is no need to bring private fields too. Just keep the same visibility rules. The new method would be written inside a user package which would have access only to the public members of the type being dispatched on. That mean that you
505.
by junke 10y ago
> Correct, they don't need to, but they couldn't anyway, as import cycles are not allowed. Package dependencies need to form an acyclic graph. I was working with those dependencies in mind: foo -> {fmt, numbers} &#x2F
506.
by junke 10y ago
Thanks for all the details. > If you could define methods anywhere, you introduce hidden dependencies and more coupling. A new package might change the nature of the type. This is not acceptable. This is the Expression Problem: adding n
507.
by junke 10y ago
> ... would be to make those private fields visible in the method outside the package. Since you write the implementation of the method inside your struct's package, you have the right to manipulate private data there as you would d
508.
by junke 10y ago
> A method defined in a new package might break a type switch (or some reflection-based code) in another package. In that case the code would break because it assumes too much. If the language was designed differently, people would code
509.
by junke 10y ago
I mean dispatch in general, not necessarily dynamic dispatch.
510.
by junke 10y ago
Compiler warning. --- (edit) The example, while being possible, looks quite improbable. If it is only a matters of conflicting names, qualified names should be able to resolve the ambiguity; here I suppose you imagine implementing the same

More ›