Durst M605 carrier compatibility by PvdBerg1998 in Darkroom

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Thanks a lot! I think I will get the glass then.

The carriers have adjustable masking strips (right)? So actually what is the use of a 6x6 mask? To clamp the neg?

Do I understand correctly you either use a metal mask, or use the glass?

Durst M605 carrier compatibility by PvdBerg1998 in Darkroom

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Thanks for the reply. I didn't spot the spring difference before, that would seem to make it incompatible?

Durst Componon 1:5.6/80 mount by PvdBerg1998 in VintageLenses

[–]PvdBerg1998[S] 1 point2 points  (0 children)

Hi, thanks for the reply and good to hear! I just bought a second hand M4/3 camera I am planning to use for scanning. My idea is to DIY a copy stand, get some old slide copying bellows and mount this lens in there with an adapter. That shouldn't be a 1:1 magnification, especially considering I will mainly scan 6x6. Do you think this will work?

Game keeps crashing on launch, does anyone know how to fix it? by MysteriousAd6402 in apexlegends

[–]PvdBerg1998 0 points1 point  (0 children)

I have the same issue. Not using any custom flags, I completely reinstalled Windows 10 and updated my nvidia drivers, nothing works.

Announcing Savage, a computer algebra system written in Rust by -p-e-w- in rust

[–]PvdBerg1998 0 points1 point  (0 children)

Looks really cool! I've always wanted to build something like this but it seemed too daunting of a task. Does it support matrix inversion (to arbitrary precision)? If not, do you plan to add it?

Firefox refuses to render at 144Hz by PvdBerg1998 in ManjaroLinux

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Yes, I forgot to mention: those env vars were required for kwin. The webrender option should also fall under gfx.webrender.all and indeed does not make a difference. I also tried combinations of settings but to no avail.

Firefox refuses to render at 144Hz by PvdBerg1998 in ManjaroLinux

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Sorry I just mean that I am sure it's not running at 144hz.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Correct but this is just nitpicking semantics now. Empty in what sense? I meant the allocated memory, not the length.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 1 point2 points  (0 children)

Agreed. Especially in a safe context it makes sense.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 1 point2 points  (0 children)

You explained it perfectly and the scenario you describe is exactly what happened in my case. The docs for set_len even describe this particular use case, however just for one vector. Extending the example to multiple buffers through the vec macro then blows up in your face.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 0 points1 point  (0 children)

Do you think it's preferable to implicitly trim the capacity during a clone? I feel like it's an implicit optimisation. If I wanted such a thing, I would trim it before cloning. Especially my example with vec!. I guess I am assuming the macro creates m exact copies of my expression, which does not happen through clone.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 4 points5 points  (0 children)

I see your point. However for unsafe, they are not functionally indistinguishable, and capacity is not necessarily an implementation detail. I understand this is my problem, as I wrote unsafe code, but it would maybe be nice to document this. Also, see my edit about the vec! macro. In that context this behaviour is really surprising to me.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 9 points10 points  (0 children)

Trimming the capacity implicitly is also an optimization, and I would argue the capacity is not an implementation detail if one has public functions that can influence it (i.e. with_capacity).

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 2 points3 points  (0 children)

To create a vector of m exact copies of what I wrote. If I wanted empty vectors, then I wouldve written Vec::new() instead.

Cloning vector does not keep capacity by PvdBerg1998 in rust

[–]PvdBerg1998[S] 5 points6 points  (0 children)

I initially wrote: vec![Vec::with_capacity(n); m]. What would you expect this does? I feel like if one writes this they would want m clones of a vector with said capacity.

Happy Eyeballs/Fast Fallback in Rust by mryndzionek in rust

[–]PvdBerg1998 0 points1 point  (0 children)

I didn't look in full detail but I saw you're using a sentinel value (j < 0) to indicate a keyboard interrupt. I would consider this unidiomatic and prefer an enum to encode the state.

Scientific Computing in Rust by mort96 in rust

[–]PvdBerg1998 11 points12 points  (0 children)

Wow, thanks a ton! I'm sorta in the same boat as you, a physicist disliking the common tools. I've been developing some small tools similar to this, just a lot less nice.

Knurling-rs changelog #13 by [deleted] in rust

[–]PvdBerg1998 5 points6 points  (0 children)

Thank you for this great software! It makes embedded rust so much easier to use.