pilotInPyjamas

Hey everyone, I'm looking to change/overhaul career mode. I'm looking for combinations of mods that work well together, to provide a unique challenge or balanced game. So far I have come up with:

• USI Suite: contains expanded colonisation, life support, resources amongst other things.
• RP-1 - This needs no introduction, but is probably too hardcore for my tastes at the moment.
• SIMPLEX contains a tech tree, kerbalism config, and a suite of other things.
• Mix and match: Kerbalism, Real Fuels, Extraplanetary launchpads. Take your pick, add mods, subtract others etc.

Does anyone have recommendations for which combinations of mods you find work well together and why?

I'm playing a no reset/no quicksave run. Lots of kerbals go missing in the name of science, so I need to do lots of rescues. Created a ship to rescue four kerbals in one go using the hitchiker. Mission goes perfectly, takes two hours. Reentry is perfect, up until the last second. Deploy parachutes. 7m/s vertical speed instead of 6m/s. Everyone dies. FML.

Now my reentry checklist includes a bailout and use of personal parachute in the case of high velocity in lower atmosphere. Lesson learned. RIP Urson, Dilgard, Megby and Julne Kerman.

Here's an idea that I've been toying around with. It's possible in TypeScript to create an index to a data structure that is only valid for that data structure. This method requires no runtime checks: it's verified completely at compile time!

I thought some people here may be interested in the pattern, and there are probably ways to refine this to be more ergonomic that I haven't thought of. This pattern takes inspiration from Rust's lifetimes and Haskell's ST

// An Array has a type and an Id
type IndexedArray<T, Id> = {
    data: T[],
    id: Id
};

// An index has an id, the id of the index must match that of the array
type Index<Id> = {
    

I don't know why I wanted to do this, and it's probably a little silly. I don't have any real world reasons to convert between Fn(T) -> T and Fn(&mut T), but I wanted to see if it was possible.

I can convert Fn(&mut T) to Fn(T) -> T, but I can't seem to go the other way around in safe rust without a trait bound on T. Does anyone know if this is possible?

EDIT: I'm going to assume that T: Sized

playground link

I'd like to know everyone's thoughts on a kind of edge case of impl Trait.

I was testing the extent of impl Trait to see how far they behave like real existential types. As a practical exercise I was wondering if it were possible to create an object that can only be used with its creator, guaranteed by the type system at compile time. For example: a vector wrapper that allows you to create an index that can only be used with that vector, and not accidentally used with any other vector (even if it has the same type).

If I relax the requirement that the check is performed at compile time, the solution is easy: generate a unique identifier for each parent. When using the parent and child

The bartender replies "Damn, those are some serious charges."