| // GLSL code for rendering numbers without using any textures or global arrays, using a tiny bitmap font | |
| // for debugging! | |
| // public domain. use under the creative commons zero license (any version) | |
| // warning: the float-to-decimal conversion logic is "incorrect" and can only give around around four or five decimal places of floating point decision | |
| // warning: the integer part of the printed floats is limited to the size of a signed 24-bit integer | |
| // GLSL code for rendering numbers without using any textures or global arrays, using a tiny bitmap font | |
| // for debugging! | |
| // public domain. use under the creative commons zero license (any version) |
Macro hygiene is the concept of macros that work in all contexts; they don't affect and aren't affected by anything around them. Ideally all macros would be fully hygienic, but there are lots of pitfalls and traps that make it all too easy to accidentally write unhygienic macros. This guide attempts to provide a comprehensive resource for writing the most hygienic macros.
First, a little aside on the details of Rust's module system, and specifically paths; it is
At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.
What killed Haskell, could kill Rust, too
What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.
Is Haskell dead?
| //Moebius transformations in 3d, by reverse stereographic projection to the 3-sphere, | |
| //rotation in 4d space, and projection back. | |
| //by Daniel Piker 09/08/20 | |
| //Feel free to use, adapt and reshare. I'd appreciate a mention if you post something using this. | |
| //You can also now find this transformation as a component in Grasshopper/Rhino | |
| //I first wrote about these transformations here: | |
| //https://spacesymmetrystructure.wordpress.com/2008/12/11/4-dimensional-rotations/ | |
| //If you want to transform about a given circle. Points on the circle and its axis stay on those curves. | |
| //You can skip these 2 lines if you want to always use the origin centred unit circle. |
| #include "particles.h" | |
| #include <assert.h> | |
| #include <algorithm> | |
| namespace particles | |
| { | |
| void ParticleData::generate(size_t maxSize) | |
| { | |
| m_count = maxSize; | |
| m_countAlive = 0; |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: