anon_342njlkesr

3 ms·

1. 1.▲
   by anon_342njlkesr 9y ago

   I had the same problem; my problem was not the giant number of reads, but rather that a naive replacement needs a read and has a dependency on the write-back; hence, a scatter where you modify immutable structures by replacing certain field
2. 2.▲
   by anon_342njlkesr 9y ago

   Re unicode: When writing latex, you don't want to encounter unicode greek sigma. You want \sigma, as 6 7bit-ascii chars. Same in julia; sure, define a display mode that translates certain things into unicode for people like you, but ke
3. 3.▲
   by anon_342njlkesr 9y ago

   Re 2: Yes, but most of the language is geared towards 1-based indexing, e.g. ranges like a:b being inclusive at the right. Hence, using a zero-based variant of array makes only sense if your code really really profits from zero-indexing. Bt
4. 4.▲
   by anon_342njlkesr 9y ago

   Yeah, the language design of julia is brilliant (multiple dispatch, typing, llvm use, zero-cost abstractions, @code_native to see why your code is slow). This allows you to write fast code in julia, which is impossible in python (you can ca