scoopr

Joined 16 years ago

Karma

689

Submissions

154

Member since

Dec 1

View on Hacker News

Recent submissions

Comment · 3 days ago

So, it’s shareware? :)

Comment · 28 days ago

Huh, I kinda thought something like this was already being done, but perhaps it was a bit later stage. Neat!

A kind of related shower thought I had, could rustc not instantiate generic methods, but write out what it expects to find (std::Vec<String>::push), and a separate build process listens to these, but makes sure already built ones are not built multiple times from the whole build.

I don’t actually know how much of duplication there usually is, but I had gotten the impression that it would be part of the problem.

Of course I’m no compiler engineer, and I’m sure there are complications like per crate build profiles, etc.

Comment · 1 month ago

Nice, always good to have some extra checking.

While most of the time you want the memcpy semantics, but I wonder if naga could be used to compute a facet SHAPE from the shader. Maybe it could be used to "serialise" the cpu format to gpu format, without them needing to be padding/repr-compatible (or even field-reorder-compatible!).

Another option of course would be to parse the struct with naga and just always generate the rust counterpart, then it should always be compatible and up-to-date, but then you have codegen in your build step.

Comment · 1 month ago

I just watched video[0] that argues if you can consteval something, then it must be free of UB, which seems compelling, at least for these lower level helpers.

Unfortunately, it seems memcpy is not constexpr, so cannot be used like this, but std::bit_cast actually works[1] as constexpr, so I think in C++ that would now be the most preferred use. It won't allow the union either.

[0] https://www.youtube.com/watch?v=-LAXqqqX274 [1] https://godbolt.org/z/xGzjTMGvv

Comment · 1 month ago

This irks me as well. There have been perfectly good words to describe these.

The models are freeware, and some have additional restrictions in the license that make them shareware, imho!

Comment · 2 months ago

I believe there are several crates (and other languages too) inspired by the original cassowary paper, don't know how mature they are though.

Comment · 5 months ago

Maybe it’s for the llm tool use PATH?

That was the most plausible reason to even mention it, that I could think of.

Comment · 6 months ago

So, is it like colinux[0], but for pre-NT windows? Neat!

Back when I was still using windows (probably XP era), I used to run colinux, it was kind of amazing, setting up something like LAMP stack on the linux side was a lot easier and then using windows editors for editing made for quite nice local dev env, I think! Could even try some of the X11 servers on windows and use a linux desktop on top of windows.

When I noticed I kept inching towards more and more unixy enviornment on the windows, I eventually switched to macOS.

Apart from the obvious hack-value, I can't quite imagine even pretend use-case, with some 486 era machine, you would be limited by memory quite quickly!