staticassertion

372 ms·

1. 4591.▲
   by staticassertion 10y ago

   About two weeks to get the majority of language features - iterators, some aspects of ownership, structs, stop fighting the borrow checker for the common cases . I was using threads to parallelize my work within the first few days, and that
2. 4592.▲
   by staticassertion 10y ago

   Zero cost abstraction has never meant anything other than 0 cost at runtime, so I don't see why you would get annoyed at it being used accuratcly.
3. 4593.▲
   by staticassertion 10y ago

   > Erlang, which is known for its reliability gets this right: kill the whole Erlang process in a clean fashion so that we can get transactional semantics. (It's not that performant though.) This is also the rust way - panics kill th
4. 4594.▲
   by staticassertion 10y ago

   This is an excellent blog post - thanks a lot for writing it up. Solid use cases defined, I particularly enjoyed how you dealt with the shortcomings of joining a relatively young language. The 'belligerent refactoring' resonated w
5. 4595.▲
   by staticassertion 10y ago

   Hmmmm. Note to self - actually try to audit a reasonably sized project's unsafe code to see how reasonable it is.
6. 4596.▲
   by staticassertion 10y ago

   Panics do not violate memory safety. In C that code would be undefined behavior.
7. 4597.▲
   by staticassertion 10y ago

   In safe rust it is definitely not trivial to overflow a buffer in a way that violates memory safety.
8. 4598.▲
   by staticassertion 10y ago

   > How do you suppose runtime bounds checks are done in Rust? They certainly also incur a performance penalty in not-trivial cases. Certainly. I didn't intend to imply otherwise. > Also, "safe by grep audit" means "
9. 4599.▲
   by staticassertion 10y ago

   Ah, I see. For what it's worth C will perform similar optimizations to Rust, which is why I expect similar performance. And thank you.
10. 4600.▲
    by staticassertion 10y ago

    While this is technically true, it isn't practically true. "Easy" is certainly false. I really enjoyed these posts by strncat: https://www.reddit.com/r/programming/comments/5krztf/rust_vs..
11. 4601.▲
    by staticassertion 10y ago

    I think this is addressed in the article when they talk about the potential pitfall of Go's GC.
12. 4602.▲
    by staticassertion 10y ago

    Totally. But in the case of rust your vulnerabilities are grep'able. For all of the code you have in a project you only have to search for the unsafe keyword when you want to audit it. I think that makes a very significant difference.
13. 4603.▲
    by staticassertion 10y ago

    People have been assuming this for years.
14. 4604.▲
    by staticassertion 10y ago

    I didn't claim that rust would be faster than C (not that it can't be) in that situation. I would expect very similar performance. I'm not feeling very well unfortunately, not really in the mood to code.
15. 4605.▲
    by staticassertion 10y ago

    If you want an AV, MSE has the lowest attack surface impact. It has always been good at implementing security mitigation techniques (whereas other vendors are atrocious here) and it's not very invasive. For security as a whole, I wou
16. 4606.▲
    by staticassertion 10y ago

    C/ C++ compilers are also capable of doing this, though rust's iterator syntax tends to make it a pretty natural optimization.
17. 4607.▲
    by staticassertion 10y ago

    Because your 'safe' implementation will certainly have a performance cost, and won't be the default. This is why, despite C++ providing std::array, you'll still find buffer overflows in C++ code. C++'s std::array pr
18. 4608.▲
    by staticassertion 10y ago

    AV = Trashfire. If there were actual repercussions for writing code irresponsibly, even their billions in revenue wouldn't keep them from bankruptcy. Time and time again we see these ridiculous vulnerabilities but nothing changes. AV i
19. 4609.▲
    by staticassertion 10y ago

    Data races definitely happen in the real world and they are awful to track down, because they only happen n% of the time. All of my least favorite bug-fix experiences have been data races.
20. 4610.▲
    by staticassertion 10y ago

    I believe you have three choices with Ada: 1) No manual memory management, everything is static and you have memory safety 2) Garbage collection, you have memory safety 3) Manual memory management, you lose memory safety Rust provides memor
21. 4611.▲
    by staticassertion 10y ago

    > Of course. But OTOH, we shouldn't immidiately discount LLs when writing code, just because the perf isn't optimal. Most of the time you should, I'd say. Regardless, the decision should be very natural/ trivial for a
22. 4612.▲
    by staticassertion 10y ago

    Right but what's the reason not to pick a data structure with better performance? This should be a really trivial choice with virtually 0 impact on code since a list and array will have nearly if not entirely the same interface. I woul
23. 4613.▲
    by staticassertion 10y ago

    Errrr, how is this lunacy? Seems like something everyone should be aware of.
24. 4614.▲
    by staticassertion 10y ago

    True, at least to some extent. But I think TensorFlow treated C++ as a first class citizen and not as a tool to improve performance. You wouldn't use sklearn as a C++ developer, for example. But you could totally use TensorFlow.
25. 4615.▲
    by staticassertion 10y ago

    Maybe they're not annoying cool kids but people doing work in a new domain and trying to share the benefits. I don't think people are saying that their solutions are better just because they're in rust. Maybe somewhere someon
26. 4616.▲
    by staticassertion 10y ago

    I did a talk at RustConf about Rust for machine learning. The short story is that rust is awesome for handling data - especially unclean data. But Python, or really anything with a REPL, is still ideal for the exploratory phase using ipyt
27. 4617.▲
    by staticassertion 10y ago

    For the record, I've used rust for machine learning, and it was great. It isn't for "religious beliefs" - both myself, an engineer, and a data scientist on my team, had great results using rust. Rust is entirely practica
28. 4618.▲
    by staticassertion 10y ago

    TensorFlow is written in C++ so I'd expect it to impact the deep learning result.
29. 4619.▲
    by staticassertion 10y ago

    This is the same in rust. Panics end at thread boundaries. So you'd have some event loop with threads / coroutines doing stuff and if they panic you handle it at the top level.
30. 4620.▲
    by staticassertion 10y ago

    You can use map or and_then, you can write a macro, you can use try!, you can use if let, etc. There are lots of ways to handle errors in rust.