gnuvince

42 ms·

391.
by gnuvince 12y ago
Notice how you're not giving an answer to Daishiman's question, merely downplaying the importance of having general data structures, though I'm sure you're quite happy that slices, maps and channels can be parametrized b
392.
by gnuvince 12y ago
The dmd compiler for D compiles faster than gc and yet supports compile-time templates.
393.
by gnuvince 12y ago
I don't really understand the comment about etags; if you use ctags in Vim, you'll get the same kind of functionality. If you want something more advanced, Emacs has support for cscope and GNU Global which give you more features.
394.
by gnuvince 12y ago
The page is 2021-ready.
395.
by gnuvince 12y ago
I've been wondering lately if the "modern" Vim setup is closer in spirit to vi from which it descends or to Emacs. Seeing as how people are trying to enable all sorts of non-editor tasks inside Vim, I'm inclined to say
396.
by gnuvince 12y ago
So, in a few thousand words, the author manages to give multiple reasons not to use Vim and not a single one to use Sublime Text, except this: > But Sublime has things Vim can never have. It’s the new hotness and has a more active commun
397.
by gnuvince 12y ago
Great job Steve! If you don't have them yet, get a copy of Strunk and White's "The Elements of Style" and Kernighan and Ritchie's "The C Programming Language". I'd love my Rust documentation to have
398.
by gnuvince 12y ago
Can we say something about using goto?
399.
by gnuvince 12y ago
As a language, OCaml gets most things right: being functional by default appeals to me very much, as does the easy path into imperative programming when you need it. Its type system is awesome not only at catching bugs at compile-time, but
400.
by gnuvince 12y ago
> is it really that hard to know how large some block of memory is, and not access beyond it? For one given block, maybe not. The problem is that in a language like C, the fallible human must get every single one correct, otherwise it
401.
by gnuvince 12y ago
I don't think that C has any safety features; there are tools to help you find where you are being unsafe (e.g. static and dynamic analysis) and tools to mitigate the effects of the unsafe code (e.g. memory randomization, canaries, etc
402.
by gnuvince 12y ago
And that's not the case with Theo?
403.
by gnuvince 12y ago
I was part of the Reddit discussion linked in the article, and although I haven't had the time to think through the issues (nor do I have the same experience as the Rust dev team), I'd like to offer some thoughts. First, I am a bi
404.
by gnuvince 12y ago
It seems unreasonable to me that you need to write out the iteration variable 3 times in a C for-loop; I had a bug a couple weeks ago that took me longer to figure out than I care to admit. I wrote `for (int j = 0; i < N; ++j)`.
405.
by gnuvince 13y ago
`undefined` is used as a placeholder for yet to be written code; since you cannot do anything meaningful with it, it is never used in practice.
406.
by gnuvince 13y ago
Emacs for me.
407.
by gnuvince 13y ago
Pretty sure your parser would need unbounded lookahead to support this syntax.
408.
by gnuvince 13y ago
So much for abstraction if you need to understand the implementation of every function you'll every use in JavaScript.
409.
by gnuvince 13y ago
Because it falls on my middle finger's knuckle.
410.
by gnuvince 13y ago
I guess, then, that you weren't part of the Battlefield 4 team [1]. I've discussed the issue of the "no decent programmer" fallacy in the past; yes, in theory if programmers were careful and alert, they could create fla
411.
by gnuvince 13y ago
A safer language with higher-level, low-cost abstractions.
412.
by gnuvince 13y ago
It's the traditional, inductive definition of natural numbers. You give a base case (Z = Zero) and an inductive case (S Nat = Successor of Nat). So Z is a natural number, S Z is also a natural number and corresponds to 1, S (S Z) cor
413.
by gnuvince 13y ago
I still think that now would be the ideal time to start working on a TLS/SSL implementation in Rust. First, it would mean that there would be less time between the release of Rust 1.0 and a usable library. It would also be a good p
414.
by gnuvince 13y ago
> The problem with C is that a lot of people don't write it well. Including people responsible for one of the most important security-related library in the world. No matter how good and careful a programmer is, they are still huma
415.
by gnuvince 13y ago
I use an GPG-encrypted .org file. With Emacs' built-in support to open GPG files, it's simple and convenient.
416.
by gnuvince 13y ago
Here's what's going to happen: neither parametric polymorphism, nor exceptions are going to happen in Go. The answer in the FAQ is just PR bullshit; the designers of Go are not interested in having parametric polymorphism and tha
417.
by gnuvince 13y ago
I used to be of the opinion that Debian stable was too old, that its packages were outdated. Then I realized that I only need Emacs 24 (compile it from source) and a recent browser (both Chrome and Firefox have up-to-date repositories). I
418.
The Architecture of the Glasgow Haskell Compiler(aosabook.org)
9 points by gnuvince 13y ago|0 comments
419.
by gnuvince 13y ago
> Yes, which is why I wonder why GHC went with it's own code generator instead of using LLVM? LLVM didn't exist when GHC was started.
420.
by gnuvince 13y ago
Most of what you learn in CS is a bunch of words you have no idea what they mean until someone gives you a precise definition. Deterministic Finite Automata, regular expression, static typing, serialization, compilation, singleton pattern,

More ›