Oh,
inspecthas finally arrived! That will help a ton with debug logging.Do you mind explaining? Maybe with the context of another languages equivalent?
let bar: Result<T, E> = ...; let foo = bar.inspect(|value| log::debug("{}", value));is equivalent to
let bar: Result<T, E> = ...; let foo = bar.map(|value| { log::debug("{}", value); value });Warning: in the first case “value” is actually a shared reference, not a value.
Elegant. Thanks!
Looks vaguely like
Stream::peekfrom Java, I think? There’s an equivalent method inIterator::inspect.it’s just a way to use map with a reference instead of the value, by what I understood.
could be usefull for logging values in a Result so you can see it. However I think you can already do that by just mapping and returning the variable.
TIL about
std::any.Congrats on another release! I’ll try it out this weekend. :)
std::anyis pretty cool. You can use it, for example, to build a map where the key is just the type of the value.So, you could query it like this:
let maybe_position = store.find::<Position>(id);The
idis the ID of anentitywhich may or may not have aPositionassociated with it.This is similar to just using structs/OOP, so where you’d have a
Vec<Entity>and then you’d callentity.position, but the big difference lies in flexibility. AnEntitytype would need to have all fields defined, which may ever exist on an entity.
With this type-as-key map approach, you can just tack on new attributes to entities and dynamically react to them.All of this is basically how the storage works in the Entity-Component-System architecture (ECS), which is popular in gamedev, for example. But both the storage method and the ECS architecture are good tools to be aware of in normal software design, too.
Yeah, I thought of runtime duck typing when I saw it, which is essentially what an ECS is.
It would be pretty cool to go the next step and be able to find and call methods or discover trait implementations on the type that may not be in the signature. So something like how Go can conditionally type asset an interface to a different interface. I don’t know if that’s possible in a zero cost way (probably not), but it would be interesting.
So rust finally gets reflection? In stable no less!
Well, if the only thing you need from reflection is the name of a type, so then yes. But I wouldn’t really call this reflection since it is very limited.
Yeah, Rust can’t have proper reflection, since there’s no external runtime environment that keeps track of your state. Any such smartness either has to be compiled-in (which is how
std::anyand macros work) or you can implement something to keep track of this state at runtime, as if you were partially building a runtime environment.Minor point of clarification: it can’t have runtime reflection, but in principle it could have compile time reflection.
No, the Rust Project recently made sure that Rust can’t have compile-time reflection.
…yeah, that’s really unfortunate. Part of why I said “in principle”.
Can you expand on this? I’d love to read more on the subject.
Here is a short summary. The compile-time reflection project was stopped, and now nobody wants to touch that subject any more due to fear of getting the wrath of the Rust project again (the person responsible for the whole thing is still part of the leadership).
And compile-time reflection will probably also continue to suck due to some irreconcilable limitations of type-safe generic specialization. Oh how I would love an equivalent to C++ template parameter packs…
Unfortunately, it’s not guaranteed to be the same string all the time, so it’s rather useless for anything but debugging and logging.
@bwrsandman @snaggen More a RTTI than reflection…
Isn’t RTTI for polymorphic classes and stored in (or around) vtables?
@bwrsandman That’s why I used ”More a” than ”Is a”… 😉
