Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)G
Posts
1
Comments
50
Joined
3 yr. ago

  • It's a very different kind of borrow checking than Rust's. For example there's no mutability xor sharing checking, because mutability cannot invalidate memory (there's still a GC in C# after all!). As such, Rust's NLL (which are available in the 2015 edition too btw) don't really make sense in C#.

  • (Note that I'm not the article author)

    In this example, you could have just made a constant with value 0 and returned a reference to that. It would also have a 'static lifetime and there would be no leaking.

    I believe the intention was to demonstrate something that works with runtime values too, and a constant 0 does not.

    Btw you can just write &0 to do what you proposed, there's no need for an explicit constant/static.

  • write only medium

    I guess you meant "write once"?


    Anyway, this won't prevent attacks that somehow swap the CD being read, or the backend logic for where to read the data from.

  • You cited Git as an example, but in Git it's possible to e.g. force-push a branch and if someone later fetches it with no previous knowledge they will get the original version.

    The problem is the "with non previous knowledge" and is the reason this isn't a storage issue. The way you would solve this in git would be to fetch a specific commit, i.e. you need to already know the hash of the data you want.

    For the Wayback Machine this could be as simple as embedding that hash in the url. That way when someone tries to fetch that url in the future they know what to expect and can verify the website data matches the hash.

    This won't however work if you don't already have such hash or you don't trust the source of it, and I don't think there's something that will ever work in those cases.

  • Lots of major companies like Microsoft and IBM also contribute to Linux, it doesn't make them saints nor even necessarily compare to what they get for using the volunteer dev work inside Linux.

    Most of those companies actually contribute to the kernel or to foundational software used on servers, but few contribute to the userspace for desktop consumers on the level that Valve does.

  • No, macros can see only the tokens you give them. They have no notion of the fact that crate::functions is a module, that PluginFunction is a trait and that functions_map is a variable. Not even the compiler may know those informations when the macro is expanded.

    If you really really want to do this, you can use something like inventory. Note that inventory uses a special linker section to do this, which some consider a hack. This is also not supported on WASM if you want to target it.

  • CEO bonuses should be awarded 10 years after their mandate

  • Would it makes sense to provide a "share nothing" runtime implementation that can be injected at startup?

    Isn't this tokio::task::spawn_local?

  • compile rust 0.7 in scala

    Not sure if there was another rewrite, but AFAIK (and the article agrees with me) rustc was originally written in Ocaml