Comments URL: https://news.ycombinator.com/item?id=46795234

Points: 4

# Comments: 1

In the "Purity and Referential Transparency" section I'd have expected some comparison with `const fn` in Rust. Aren't `const fn` in Rust pure?

Without mypy cache:

  $ rm -rf .mypy_cache
  $ time mypy
  Success: no issues found in 157 source files
  mypy  20.40s user 2.33s system 108% cpu 20.886 total

  $ mypy --version
  mypy 1.16.0 (compiled: yes)
  $ time mypy
  Success: no issues found in 157 source files
  mypy  0.56s user 1.84s system 628% cpu 0.381 total

  $ time mypy
  Success: no issues found in 157 source files
  mypy tests/  2.32s user 2.06s system 168% cpu 2.601 total

  $ time zmypy
  Found 68 errors in 16 files (checked 157 source files)
  zmypy  0.68s user 0.05s system 99% cpu 0.731 total

zmypy seems to find more errors but they mostly boil down to the following errors

* Call to untyped function "__setitem__" in typed context

* ... has incompatible type "MagicMock"; expected ...

Maybe __setitem__ and MagicMock are treated specially in mypy? Also there seem to be differences in handling Protocol and enum comparison.

> for the first time, we have a Rust-based driver in the mainline kernel.

https://rust-for-linux.com/amcc-qt2025-phy-driver is in mainline since 6.12 and https://rust-for-linux.com/asix-phy-driver even since 6.8

> empowers Nvidia's next-generation open-source graphics hardware. The driver targets Nvidia's RTX 2000 "Turing" series and newer GPUs.

This sounds like it is already fully working, but as far as I know it's just a stub driver merged so far: https://rust-for-linux.com/nova-gpu-driver, https://www.phoronix.com/news/NOVA-Driver-For-Linux-6.15

This makes the article appear as just click-bait to me.

So far I just pinned the rustc version used by requiring rustup as a build dependency. Let's see if this lets me drop it or if it is still easier in the end to build with pinned version.

There are donation buttons for some artist on Spotify. I guess the artist need to enable it? ("Signum Regis" is an artist that has a Donate button for example)

Comments URL: https://news.ycombinator.com/item?id=39920522

Points: 3

# Comments: 2

The offficial Rust compiler is written in Rust.

> And where can I download bootstrap static ELF64 binaries of this compiler?

You can get a Rust compiler on https://rustup.rs

Probalby you can get one which is statically compiled for the musl target.

If you want to follow the boostrap procedure see https://rustc-dev-guide.rust-lang.org/building/bootstrapping...

* https://blog.rnstlr.ch/building-an-out-of-tree-rust-kernel-m...

* https://blog.rnstlr.ch/building-an-out-of-tree-rust-kernel-m...

Comments URL: https://news.ycombinator.com/item?id=36339762

Points: 4

# Comments: 1

Well you can implement a trait for a type from another logical part either in the crate of the trait or the crate of the type.

What is the use-case for implementing a foreign trait for a foreign type if you have both under control?

I usually put the traits in a separate crate, but keep concrete types and implementations for them in the same crate.

What is the use-case for splitting a type and it's implementation into separate crates? (except for cases where the trait or the type are out of your control, then one indeed needs to use the new-type escape hatch)

Maybe the allocations were the reason?

But you probably won't learn much Python by using it (or Rust when using a generator written in it) since you probably won't need to change anything in it. The only Python code you need to write for Pelican is the configuration, which is just setting a few variables.

* https://blog.rnstlr.ch/building-an-out-of-tree-rust-kernel-m...

* https://blog.rnstlr.ch/building-an-out-of-tree-rust-kernel-m...

I'll probably make a follow up post with Linux 6.2

This post does a lot better job at describing the prerequisites to enable Rust in the Linux kernel, while I just referred to the AUR package I created.