-
```
I think "fast" types are supposed to allow fast operations (basically,
efficiently use the registers) on the target machines.
Example: int_fast16_t is currently defined as 16-bit integer, which …
-
```
I think "fast" types are supposed to allow fast operations (basically,
efficiently use the registers) on the target machines.
Example: int_fast16_t is currently defined as 16-bit integer, which …
-
```
I think "fast" types are supposed to allow fast operations (basically,
efficiently use the registers) on the target machines.
Example: int_fast16_t is currently defined as 16-bit integer, which …
-
```
I think "fast" types are supposed to allow fast operations (basically,
efficiently use the registers) on the target machines.
Example: int_fast16_t is currently defined as 16-bit integer, which …
-
### Bug description
I couldn't find and specifications on how large the type Int is (and if it's signed)
so I fooled around in the Mojo Jupyter notebook with some large numbers like this:
```
le…
-
It inherits `_add_` and `_sub_` methods that make no sense in the coercion system. These methods are guaranteed by the coercion system to get elements of the parent, and are supposed to give element…
-
Based on #2 GNU Bash Indexes Definitions
# Mandatory
- token: word | operator
- word: A sequence of characters treated as a unit by the shell (may not include unquoted metacharacters)
- operator…
-
I found several problems with complex interval arithmetic:
1. It seems that it takes the dilog of the midpoint and then converts it back to intervals:
```
sage: dilog(CIF(RIF(4,4.1),RIF(4,4.1)))
-…
-
Just something I came across while working on #46 - i'm not sure if this is desired behaviour or not
-
```c++
NumericT int32FromLEOffset(NumericT * start){
return int32From2Int16(int16FromLEOffset(start), int16FromLEOffset(start + 2));
}
```
and generally
```c++
NumericT intNLEFromOffset(Nume…