If you are interested to bring more SIMD instructions, you can participate in the SIMD subgroup. What's needed is interest in suggesting new instructions, working on a proposal (following the process) and pushing it through. Compiler expertise not required :)
2 classics that don't require a whole lot of backgrond are:
- An Axiomatic Basis for Computer Programming by C. A. R. Hoare
- The Next 700 Programming Languages by P. J. Landin
The most recent paper I've read is:
- Storage strategies for collections in dynamically typed languages - Bolz, Diekmann, Tratt
I blog about some papers I've read on my blog [0], and these three papers I've mentioned have their own post, where I summarize key ideas of the papers. Take a look if you're interested.
The SQL version reads left-to-right, similar to how ReQL's version reads top to bottom, and both reflects the execution order (in terms of a common way of text flow). From my understanding, ReQL does not do any form of optimization based on the complete query, the `.()` punctuates the flow of command. Whereas and SQL statement is just one compound thing made up of different commands where the SQL engine can optimize, which makes it hard to tell.
Tests that relied on date (especially involving getting the current date) are usually hard to get right. I had an assignment in school to build a To-do list, and had lots of problems trying to test it. I think I solved it by having methods take 2 dates, initial and relative date, rather than just getting the current date.
Oh wow, that is a pretty bothersome trouble. I don't know nearly enough about databases and generating reports to understand this, but that link is saved. Thanks for sharing!
Yes many sites do require that, but Yahoo? I expected a little more from them, does it even make any sense to have such password requirements anymore?
Also, I can't tell for sure if the phone verification is optional, it could be required for new sign ups randomly.
Yea I most definitely can, but I will definitely don't feel like logging in anymore.
If you are interested to bring more SIMD instructions, you can participate in the SIMD subgroup. What's needed is interest in suggesting new instructions, working on a proposal (following the process) and pushing it through. Compiler expertise not required :)