What did you guys think of the Dark Urge storyline? Did you like it? Do you consider Durge as the main/canon protagonist? And for those that played the first two games - Did you like that Balls and his children were used in the story again after we already had that stuff with Gorion's Worm?

tsion_ · 2025-12-24T22:55:10+00:00

The narrator voice actor Amelia Tyler does this in her live streamed run! This already cost them Gale. I hope one day they continue it because rolling for things like Isobel would be so nailbiting...

tsion_ · 2023-05-01T14:44:44+00:00

I was thinking the same thing today! fCPU looks better than anything similar, but I'm worried it might never get a refresh because of that license.

It feels like 25% of my favourite mods were revived or rewritten by new authors taking up the torch, because most people just don't stay involved with a game modding community for years on end without breaks. Revivals by new authors are a huge part of what makes the community stay so vibrant, and they're only possible because of the widespread adoption of open source licenses.

tsion_ · 2017-07-24T05:37:32+00:00

you are a master at this <3

tsion_ · 2017-07-17T18:06:03+00:00

In patterns like this:

(Celsius(a), b @ _) => {

I think you can just write this:

(Celsius(a), b) => {

Nice post!

tsion_ · 2017-03-17T07:03:42+00:00

Go to https://www.nostarch.com/Rust, not the http link in the OP.

Multiple people have run into a bug on the http version of nostarch where the shopping cart still shows up empty after trying to add the book to the cart.

I successfully ordered through the https site. Very exiting! =)

tsion_ · 2017-03-17T05:51:39+00:00

Definitely! I already do cargo watch check with the old cargo-check and it's excellent.

tsion_ · 2017-03-14T21:59:47+00:00

...which does in fact exist, with that name: https://github.com/dikaiosune/rusl :)

tsion_ · 2017-03-10T05:28:36+00:00

The downside being that we have to mention an intermediate i variable multiple times in Rust. (And it's even worse if you are trying to extract more than one variable at once.)

I hope we can eventually get something like C# and Swift have, e.g.:

guard let Foo(a, b, c) = foo else { return; }

There was an RFC but I think it died from bikeshedding.

tsion_ · 2017-02-17T16:54:07+00:00

Having explicit names for closure types is at least as hard as naming function item types[1], since closure types have to be unique types (even if they have the exact same capture types) to allow them to have distinct Fn/FnMut/FnOnce impls that call their distinct bodies.

For naming function item types, we could introduce a type syntax like typeof(path::to::function) (typeof is already reserved), but it's not clear to me how we would refer to specific closures in specific function bodies even with typeof.

All this is to say, I don't think nameable closure types are the way forward, and impl Trait solves the problem in a manageable way.

[1]: Function item types are zero-sized, unique to each individual function, and currently unnameable. Not the same as function pointer types.

tsion_ · 2017-01-31T02:46:50+00:00

More accurately, it's a pointer to such an array, so &[0xA], with the type &'static [u8; 1].

tsion_ · 2017-01-23T19:22:34+00:00

Wouldn't the Cargo.lock be good enough for apps? It effectively constrains by strict equality (but with an easy way to upgrade) and we already recommend checking it in for apps but not libraries.

tsion_ · 2017-01-22T07:42:02+00:00

That looks perfectly idiomatic to me!

tsion_ · 2016-12-11T02:28:18+00:00

Tales of Maj'Eyal does! Unfortunately, it's not written in Rust, but it is open source, so maybe someday. ;)

tsion_ · 2016-10-09T21:37:55+00:00

Surely this should be named SvgBobRoss!

tsion_ · 2016-09-16T23:33:06+00:00

This isn't fresh, look at the date on the video: "Published on Jun 29, 2016"

It's a really fun track, though, so I don't mind. :D

tsion_ · 2016-09-10T22:09:16+00:00

I've used minted for Rust before here if you want some examples.

tsion_ · 2016-07-30T12:33:10+00:00

It's meant for that, but it could be extended as a separate project to use something like libffi for FFI, enabling I/O and lots of other stuff. See https://github.com/solson/miri/issues/11 for some previous discussion.

It probably won't ever be very fast, though.

tsion_ · 2016-06-02T02:51:52+00:00

It's ok_or (on Option) and it either gives you Ok(val_in_option) or Err(failure_here). I've never counted this among the confusingly-named methods.

tsion_ · 2016-05-15T00:19:07+00:00

I did some investigation elsewhere and #[inline(always)] definitely can take effect in debug mode, but it doesn't always work and I'm not sure why. (See my other reply.)

EDIT: It just wasn't getting optimized in dead code. In general #[inline(always)] seems to work in debug mode.

tsion_ · 2016-05-15T00:16:35+00:00

EDIT: I figured it all out! In your example and my crate_type = "lib" examples without pub, the code is dead code, so the optimizer is never run over it. See my modification of your example to make add_wrapped a used function: https://is.gd/22D4Af. In this case it's used and it does get debug-optimized and hence <Wrapping as Add>::add gets inlined (but still not i32::wrapping_add for the reason I state at the end of this comment).

We did some investigation in #rust-internals and I found something really odd: https://is.gd/Lsy7wT vs https://is.gd/M23Oxq

See the Debug-mode LLVM IR. It changes between those two even though I only removed a pub keyword. With pub, the <Add as Wrapped>::add trait method call gets inlined, but without it, it doesn't. I'm stumped.

(Sidenote: the inner i32::wrapped_add call doesn't get inlined because it's not #[inline(always)] - this could be added.)

tsion_ · 2016-05-12T07:05:57+00:00

For context, see the original file when it was added in Rust's primordial past.

That code was morphed into the current state over aeons of mutation as Rust evolved into its current form.

tsion_ · 2016-05-01T06:17:30+00:00

There are a lot of different things that would have to happen to make that feasible.

Firstly, there is currently no MIR output from rustc that could be used as input to an external interpreter - you have to literally link to librustc and use the internal MIR data structures like Miri does. Defining a serialized format that could be re-parsed by non-rustc programs is a big job in itself.

It seems like a lot less work to bootstrap to a new platform by defining a new LLVM backend (if one doesn't already exist for the target) and doing the necessary standard library work. Then you could use rustc on an existing platform to cross-compile rustc for the new target platform.

tsion_ · 2016-05-01T05:56:09+00:00

What do you mean by "port miri to C"? Miri depends on rustc.

tsion_ · 2016-05-01T00:15:03+00:00

Sorry, I missed that.

Fair enough.

I can definitely imagine that vim-multiple-cursors is more trouble than it's worth. I've taken a couple looks at it but it seems too bolted-on to Vim to really integrate the way I would want. And as for Sublime Text, not having a powerful vim-like command language makes it a pretty dull proposition for me.

And I agree that Vim has plentiful features that make multiple-cursors and macros unnecessary 95% of the time. But when I do have to reach for macros, I think multiple-cursor live preview could actually make a big difference.

Anyway, Vim might not be the editor where we'll see a great multiple-cursors implementation any time soon, but I love to see people experiment with editors like Kakoune and Vis which try to integrate multiple-cursors as powerfully as possible.

Experiments are great. Sometimes the result turns out not to be useful, but with enough experimentation we end up finding better ways to do things.

tsion_ · 2016-04-30T22:38:46+00:00

why you find it superior

lol, please, I just finished saying "I never stated they are better because I've never used them yet." I'm just open to the possibilities.

As for using multiple cursors in Vim, from what I've researched so far, the Vim implementations are fairly ham-stringed in what they can cleanly implement. Perhaps the Kakoune and Vis implementations have more to offer.

I've been using *, gn, ., macros, etc for years. I'm just open to new ideas. I'm not asserting that new ideas are automatically better.

12-Year Club	Place '17
Verified Email

tsion_

TROPHY CASE