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/)A
Posts
1
Comments
277
Joined
3 yr. ago

  • Reminds me of a nazi in Germany that had his friend hack of some of his fingers to blame it on radical leftists.

  • If you want your 1.5 acres, you better not complain that the bus comes twice a day and the only doctor in the area retired 3 years ago.

  • Deleted

    Permanently Deleted

    Jump
  • If you buy a ticket last minute for a high speed train it will stay expensive. Train people want you to be predictable, so book ahead and pay around half price.Slower trains will obviously be free at point of use.

  • He wanted to show that AC lines with their heigh voltages are dangerous, as he sold low voltage DC power.

  • Webp

    Jump
  • This doesn't change it to a png, but your image viewers recognize it as webp. You should just associate .wepb with your image viewer in the OS.

  • Deleted

    Permanently Deleted

    Jump
  • Swedish developer of the year

    Don't get me wrong, he does great work, but your post should mention it somewhere.

  • Rust doesn't allow type inference in function signatures, c++ does with auto. IIRC, they recommended against using it, because of -you guessed it- compile time.

  • Deleted

    Permanently Deleted

    Jump
  • I know, but otherwise there is no use for the knowledge that we live in a simulation. Unless someone can contact the outside of course.

  • Deleted

    Permanently Deleted

    Jump
  • The only thing one could do with knowledge of being in a simulation, is trying to find bugs and exploits.From now on, I expect anyone claiming we live in a simulation to have a working perpetual motion device, faster that light communication, or something similarly impressive. If they don't, their claim is meaningless useless.

  • But you’re also missing one use of the impl keyword: fn func() -> impl Trait.

    [...] So dropping the impl in [return position] might not be completely impossible like the other uses of impl.

    But the impl markes that it is a trait to the programmers.Take the following functions:

     
        
    func1()->A{...}
    func2()->A{...}
    
    
      

    Does the following snippet compile?

     
        
    let mut thing = func1();
    thing = func2();
    
    
      

    Under the current rules we know it will. But if A could be a trait, the functions could return different types. We currently mark that with the impl.


    Why? What value does -> () provide? Why not elide that?

    What value is provided by keeping it?

    What value does cluttering up your code with -> () provide?

    Why a syntactic special-case for exactly that type and not any other random type?

    Because the unit type is special, just like the never ! type. () also has the special importance of being the return value of an empty statement and some other stuff.


    languages w/o [semicolons] feel awkward since you’re generally limited to one statement per line

    Then fixing that might make sense. :-)

    It's fixed with semicolons ;-)

  • If the spec contains default values why not make a constructor with all the missing fields or implement Default when all fields are covered?

    Also lol:

     
        
    #[test]
    fn test_config_load() {
        todo!();
    }
    
    
      
  • And considering the content of the "comics", one set up to glorify AGI as our lord and savior.

  • Should have gone with the rising star cave, with the homo naledi fossil location.

  • This H. sapiens didn't even italicize properly.

  • You could save 0.64 bit per char more if you actually treated you output as a binary number (using 6 bits per char) and didn't go through the intermediary string (implicitly using base 100 at 6.64 bits per char).This would also make your life easier by allowing bit manipulation to slice/move parts and reducing work for the processor because base 100 means integer divisions, and base 64 means bit shifts. If you want to go down the road of a "complicated" base use base 38 and get similar drawbacks as now, except only 5.25 bits per char.

  • Unless you only copy and compare you have to decode it, or implement more complicated logic for everything from searching to concatenation (which is normally just memcopy).