I'm glad to see someone thinking about supporting SIMD address spaces. Obviously, if operating on higher dimensional integers and floats is faster and better, then operating on higher dimensional pointers must be faster and better too.
And while we're at it, we should probably add support for <strong> types, to help guide the optimiser to the types we know need the most optimising, and <em> types for those that need to be inlined entirely. Ooh, we can use <span style="color:red;"> as an additional indication of unsafety!
We could repurpose <marquee> for lazily evaluated types or something to do with continuation passing style. After all, <marquee> is not broken if you change the part that hasn't been displayed yet.
Ooh, we can use <span style="color:red;"> as an additional indication of unsafety!
No way! You should use <span class="unsafe"> instead. <span style="..."> should be used for structural types only, and unsafety is orthogonal to structural types...
Wait, wait wait wait. I've got it! We'll use style attributes to control rustfmt! That way, we can have perfectly formatted, beautiful code with just a few thousand HTML tags! It's genius!
That said, I don't like the use of class. Everyone knows Rust doesn't have OOP.
I'm glad to see someone thinking about supporting SIMD address spaces. Obviously, if operating on higher dimensional integers and floats is faster and better, then operating on higher dimensional pointers must be faster and better too.
And while we're at it, we should probably add support for
<strong>types, to help guide the optimiser to the types we know need the most optimising, and<em>types for those that need to be inlined entirely. Ooh, we can use<span style="color:red;">as an additional indication of unsafety!Such possibilities...
I propose
<blink>to denote existential types. Alas, I have yet to think of any use at all for the<marquee>tag...Isn't it obvious? Streaming types. They come in one side, go out the other.
Proposal: replace
Iterator<Item=T>with<marquee>T</marquee>We could repurpose
<marquee>for lazily evaluated types or something to do with continuation passing style. After all,<marquee>is not broken if you change the part that hasn't been displayed yet.No way! You should use
<span class="unsafe">instead.<span style="...">should be used for structural types only, and unsafety is orthogonal to structural types...Wait, wait wait wait. I've got it! We'll use
styleattributes to controlrustfmt! That way, we can have perfectly formatted, beautiful code with just a few thousand HTML tags! It's genius!That said, I don't like the use of
class. Everyone knows Rust doesn't have OOP.Meh, that's short for
type-class. It's paying homage to the Haskell influence.I hope
<script>types are considered. I like the idea of using flow and typescript to type my type metapeogramming javascript.[deleted]