| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  |  | 
|  | Use more C++17 features where this helps any. | 
|  |  | 
|  | - use `static constexpr inline' to avoid requiring
  explicit declarations in object code
- use `const Foo* const' to maybe put into readonly
  binary segment (at least for ELF DSOs)
- `constexpr' in function scope has storage, avoid
  `static'
- don't use `constexpr' where there's no advantage,
  like arrays
We'd like to avoid overhead of atomic initialization
for each function call. No idea how `static constexpr'
requiring storage in the standard plays with atomic
initialization requirement. Hearsay points that
`constexpr' without `static' in block scope behaves
more to our liking. It's all hazy though.
I'm not 100% sure if `static inline constexpr' has any
storage. Hopefully none, like a #define, and stuff
bigger than registers gets coalesced within the same
module, with small stuff being immediates. | 
|  | Adjust usages. | 
|  |  | 
|  | I haven't even compile-tested Linux and OSX-specific bits. | 
|  |  | 
|  |  | 
|  | It underflowed cause of our high dt.
Also get the smallest difference over the screen, for HMD devices.
Allow for very low-sensitivity operation.
Issue: #523 | 
|  |  | 
|  |  | 
|  | Adjust usages. | 
|  | Always use the shorter way around.
This also adds a sensitivity param.
Issue: #370 | 
|  |  |