untothebreach

Ah, you're right, sorry. Corrected.

There is a postponed issue regarding them here: https://github.com/rust-lang/rfcs/issues/811

(Edited after @steveklabnik corrected me)

I have had great luck with Brother drivers on all the linux machines I've ever tried to use them with, so I would consider that a good option as well.

mainly just, "how to deference the address you just got to get the value you want." Might be covered under the "syntax" heading as well, but the concept was still gone over for those that hadn't quite grokked it yet.

Well half the devs call it "little-c" but the other half call it "clang," and what do you mean there is already something called clang?

I can't speak for jvns, but for my degree, "UNIX BASICS" was essentially "Command-line basics" (an intro class), and Assembly was pretty much just the actual language syntax, registers, pointers, and interrupts. The word "syscall" might have been mentioned once or twice, but only in a hand-wavy, "don't worry about this right now" kind of way.

A prominent member of the rust community has been publishing a series on getting rust to target their Uno: http://jakegoulding.com/blog/2016/01/02/rust-on-an-arduino-u...

It depends on the state, though most are "at will." Some companies will do a "trial period" in which some of your benefits are held back for anywhere from 60-90 days, so that may be what the parent is referring to.

off the top of my head, I would say it's similarity to Ruby means that Ruby devs would have an easier time learning the language than learning an entirely new one. Crystal also seems to have an extensive standard lib, which lua does not. (that's not a criticism of lua, just an observation. I know luarocks has made the lack of a large stdlib much less of a pain point for lua)

I used both nim (back when it was still nimrod) and rust for a while, before eventually settling on rust. I tried to give nim a chance, and was told that "they will grow on you" ("they" being the things you mentioned that were "unique decisions instead of what you're used to from other languages"). They never did, and though I got used to avoiding the problems I initially had with them, the language just never "felt good" to me.

Indeed, C <-> Rust interop is one of rusts design goals. The Rust Book goes over this a bit: https://doc.rust-lang.org/book/ffi.html#calling-rust-code-fr...

Thanks for pointing out my "y'all" typo -- fixed. I just don't like the way "y'all" rolls off the tongue, and never enjoyed using it. But, as you say, there has to be SOME second person plural. I just like the way "yinz" sounds, I guess. /shrug

Really? That's disappointing. I'm going to edit my post a bit bc apparently I've been misled :-/

My wife talks this way all the time, and when we were first dating it really bothered me. Eventually I came across an explanation of the regional-ness of it on the internet somewhere, and I asked her if any of her family is from the Pittsburgh area. As far as she knows, they aren't, but they are from Columbus, OH, which is just down the highway a bit.

I heard that Pittsburgh-ians also tend to use "yinz" for the second-person plural, which I find much better than a plain "you," and much, much better than "You all" or "y'all". (Though I'm now told it is not as commonly used as I assumed it was)

Anyway, I love reading about the various ways american english has diverged, given time and distance.

Not sure if this fits the bill, but you can do code generation at compile time with cargo using build scripts: http://doc.crates.io/build-script.html

I have an as-yet-unpublished crate that takes a JSON API spec and generates an API client for it (in rust) at compile time using this method.

Came here to say this. I learned so much that I didn't previously know about WWI from HH. Not only the military history aspect, but the political and cultural context for a lot of it.

I don't really understand this issue. If I write a one line function in rust, nested within another function, I will use a closure. Which, incidently, rarely requires me to annotate any types.

I assume @ComNik is referring to core.schema and core.logic[1] here, respectively? (if not, sorry @ComNik)

1: https://clojure.github.io/core.logic/

the point that has been known for decades is not, "Switching from Node.js to Go gives you better performance," it is "switching from a high-level language to a low-level language gives you better performance." This point _has_ been known for decades, but new generations of programmers keep re-discovering it. (note: I am not critizing new programmers, I am one of them. in fact, having recently switched from python to rust, you could say I am one of the many re-discovering the performance joys of lower-level languages)

This is really great, thanks for posting this!

I believe that, what he wants us to take away from this, is that once he "proves" himself to be who he says he is, his life will change in ways similar, but worse, to the ways that it has since he claimed to be Satoshi. It is this change, he seems to be saying, that he is not courageous enough to face.

Sounds like B.S. to me, but who tf am I to judge?

About a year ago I made Rust bindings, but they are out-of-date now, as I kind of stopped participating in the wren community (not their fault, I stopped participating in a lot of communities due to some happenings in my personal life). I will have some more time coming up here soon, and hope to get back into it.

It looks like the last bullet point on the page, so I'm not surprised that you missed it. They could definitely put this farther up the page:

"Wren is a scripting language. Wren is intended for embedding in applications. It has no dependencies, a small standard library, and an easy-to-use C API. It compiles cleanly as C99, C++98 or anything later."

http://munificent.github.io/wren/

My understanding was that implementing this is dependent on MIR fully landing, is that correct?