staticassertion

236 ms·

4651.
by staticassertion 10y ago
This was the subject of the talk that I gave with a cospeaker at RustConf. Effectively, the shortcomings of dynamic type systems when it comes to building data science oriented services. You mention that it's much omre laborious to wri
4652.
by staticassertion 10y ago
Been using rust for months now and I never knew the [-] did that. I never even thought to click it. Seems like there's some UX improvements that could happen there.
4653.
by staticassertion 10y ago
Feel free to stop by the IRC and ask questions/ seek help - lots of people there who are willing to answer your questions. Or the rust forums: users.rust-lang.org Or the rust subreddit: reddit.com/r/rust
4654.
by staticassertion 10y ago
Well... how do you know the code is safe otherwise? Exhaustive tesitng is unreasonable. How do you ensure that you have achieved the end goal of safe software?
4655.
by staticassertion 10y ago
In that case you may want "expect" over unwrap.
4656.
by staticassertion 10y ago
Even in a library there are valid use cases for an unwrap. If you can literally guarantee that the value is present it's fine. In libraries one should be wary about it, and never use it if the unwrap might actually panic, but otherwise
4657.
by staticassertion 10y ago
Thanks a lot.
4658.
by staticassertion 10y ago
> This is not quite accurate as stated: the problem is the combination of a data structure that is not amenable to type inference with an API that would only be efficient if type inference had perfect knowledge of the contents of a DataF
4659.
by staticassertion 10y ago
I think that if this were true, the data science libraries in Python wouldn't all be written in C under the hood, linking to Fortran, etc. Language can have a huge impact on performance with big data. Julia is just a small step forward
4660.
by staticassertion 10y ago
Like what? I assume you're referring to testing. Tests are a way to ensure that for some set of inputs you will get some set of desired outputs. And this is assuming you wrote correct tests. Types are far more rigorous - you can ensure
4661.
by staticassertion 10y ago
"Type errors" go way further than "Damn, I passed a string in where I expected an integer". Types are a way of expressing aspects of your code. You can avoid race conditions, you can ensure a program's state is alwa
4662.
by staticassertion 10y ago
What is it you're referring to when you say 'model' ?
4663.
by staticassertion 10y ago
> If they were going to run the whole thing in a SECCOMP container anyway, there is little damage a compromised C library could do. True, especially since they appear to be using a traditional seccomp sandbox, which means the process rea
4664.
by staticassertion 10y ago
I don't think C++ can statically constrain use after move. A moved value is considered valid, but unspecified. It is entirely possible to use the value after moving it, though maybe there's a warning? Using Unique Ptr it's a
4665.
by staticassertion 10y ago
"You can do this in almost any typed language that lets you consume things." True, but languages with support for affine types are, to my knowledge, uncommon. "One problem is where to put your state-specific type info when yo