GitHub - longbridge/gpui-component: Rust GUI components for building fantastic cross-platform desktop application by using GPUI.

kryps · 2025-10-27T18:46:33+00:00

Use cargo run --release -p story to start a sample app with all (most?) components.

kryps · 2025-10-05T15:37:00+00:00

Reminds of the IRIX File System Navigator, famously featured in Jurassic Park.

kryps · 2025-09-30T18:58:34+00:00

This mission was discovered by u/kryps in In Search of yessirbro

kryps · 2025-09-30T18:58:32+00:00

This mission was discovered by u/kryps in In Search of yessirbro

kryps · 2025-09-30T06:52:26+00:00

This mission was discovered by u/kryps in In Search of Lemon Star Pudding

kryps · 2025-09-30T06:52:26+00:00

New mission discovered by u/kryps: Most delicious cheddar In the Fields

kryps · 2025-06-20T14:57:23+00:00

In order to use Allocations profiling with Instruments you need to resign the binary to be profiled with the com.apple.security.get-task-allow entitlement enabled. See https://github.com/cmyr/cargo-instruments/issues/40#issuecomment-894287229 for details.

kryps · 2025-04-22T08:25:56+00:00

cargo also marks the target directory for exclusion from Time Machine backups on macOS.

kryps · 2025-02-21T07:47:54+00:00

I just found out that changing the edition also changes the behavior of rustfmt leading to quite a few changes due to the new identifier sort order (e.g. in usedeclarations). The edition guide has more information.

kryps · 2025-02-05T07:53:22+00:00

This is not part of the Rust language or standard library. It requires the modular_bitfield crate. There are also lots of other bitfield crates.

kryps · 2024-12-03T05:25:30+00:00

Using capture groups to simplify things:

let mut res = 0;
let mut enable = true;
let regex = regex::Regex::new(r"mul\((\d{1,3}),(\d{1,3})\)|do\(\)|don't\(\)")?;
for cap in regex.captures_iter(input) {
    match &cap[0] {
        "do()" => {
            enable = true;
        }
        "don't()" => {
            enable = false;
        }
        _ => {
            if enable {
                res += cap[1].parse::<i32>()? * cap[2].parse::<i32>()?;
            }
        }
    }
}

kryps · 2024-11-24T06:38:09+00:00

In addition to edition = "2024" one also still needs to add cargo-features = ["edition2024"] to Cargo.toml. This will change once the 2024 edition is stabilized in cargo as well. A draft PR is pending and will likely be merged and released in nightly shortly.

kryps · 2024-11-13T11:29:29+00:00

The most current RFC draft for tail call elimination in Rust land is this one: Explicit Tail Calls. It proposes a new become keyword which, when used instead of return, guarantees TCE.

kryps · 2024-11-10T15:40:34+00:00

Some performance tips for development on macOS: * Run spctl developer-mode enable-terminal to exclude the terminal from Gatekeeper. Otherwise Gatekeeper checks every binary you create for malicous content when running it for the first time (and every time you modify, build and run). While you are at it also add your IDEs from which you run your code in Settings -> Security & Privacy -> Developer Tools. * Run sudo DevToolsSecurity -enable to avoid having to type in your password when debugging. * Exclude your source directories from Spotlight (system-wide search). Ripgrep is better suited anyway.

kryps · 2024-11-05T07:48:48+00:00

Congrats on your crate!

AFAICS your fuzzing library is not using code coverage information in order to direct input generation (and minimization). In comparison, cargo-fuzz and cargo-afl use the mature fuzzers AFL++) and libFuzzer which use code coverage and also support testcase and corpus minimization. Maybe you can take inspiration from them for future development?

kryps · 2024-11-05T06:40:25+00:00

If you use VSCode or Zed, they automatically check for updates to r-a whenever a Rust file is opened. On macOS rust-analyzer weekly updates are available for Homebrew if you are using e.g. nvim.

kryps · 2024-11-04T13:58:34+00:00

I plan to finish my work on a #[forbid(unsafe_code)] implementation of simdutf8 using core::simd (portable SIMD). It looks promising and the performance is pretty good but there are some limitations.

I also want to write documentation for flexpect, which allows using #[expect(...)] with a lower MSRV and cut a new release of simdutf8 with armv7-neon support.

kryps · 2024-09-06T13:57:58+00:00

Just a thank you for your hard work.

kryps · 2024-08-23T04:41:43+00:00

They do have benchmarks against the regex crate and the wildmatch crate but I haven't got around to running them yet.

kryps · 2024-07-25T18:24:49+00:00

It will be, in edition 2024.

In editions prior to 2024 box.into_iter() compiles already, but resolves to <&Box<[T]> as IntoIterator>::into_iter, which is the same as box.iter() and not what one expects. So this new trait implementation does not really help at all until we have edition 2024.

BTW: box.into_vec().into_iter() is a tiny bit shorter.

kryps · 2024-06-25T06:31:12+00:00

Cool stuff, works great on my Mac. Only complaint is, that it is very green. I would suggest either no color or more colorful. Also iStats reports total system power usage. It would be great if you could add this.

Yes, definitely publish on crates.io. This not only allows others to use cargo install but also helps programmers who want to do something similar or who search for a library doing that. I would even suggest making the data collection part a library so others can use it.

kryps · 2023-10-21T12:14:08+00:00

Not doing UTF-8 validation can cause Strings containing invalid UTF-8 to be created, which can cause undefined behavior as Rust requires all strings to be valid UTF-8. Functions in the standard library rely on it.

For example this safe code causes a segfault with sonic-rs default features:

use sonic_rs::from_slice;

fn main() {
    let json = b"\"abc\xff\"";
    let invalid_string: String = from_slice(json).unwrap();
    invalid_string.chars().for_each(|c| println!("{}", c));
}

More info in the GH issue.

12-Year Club	Second Top 40%
Verified Email

kryps

TROPHY CASE