parent
5cee6220b3
commit
95c6aa65ea
|
|
@ -1,85 +0,0 @@
|
|||
## Types
|
||||
|
||||
### Primitive data types
|
||||
|
||||
Primitive data type are the building blocks of which other more complex
|
||||
types are derived from. Each primitive type has the following 3
|
||||
attributes:
|
||||
|
||||
1. **Type:** Indicates the name for the type
|
||||
2. **Width:** How many bits it takes up
|
||||
3. **Intended interpretation:** How it should be interpreted
|
||||
|
||||
#### Integral types
|
||||
|
||||
| Type | Width | Intended interpretation |
|
||||
|----------|-------|---------------------------------|
|
||||
| `byte` | `8` | signed byte (two’s complement) |
|
||||
| `ubyte` | `8` | unsigned byte |
|
||||
| `short` | `16` | signed short (two’s complement) |
|
||||
| `ushort` | `16` | unsigned short |
|
||||
| `int` | `32` | signed int (two’s complement) |
|
||||
| `uint` | `32` | unsigned int |
|
||||
| `long` | `64` | signed long (two’s complement) |
|
||||
| `ulong` | `64` | unsigned long |
|
||||
|
||||
#### Decimal
|
||||
|
||||
TODO: Add this
|
||||
|
||||
- float32, float64 etc
|
||||
|
||||
------------------------------------------------------------------------
|
||||
|
||||
### Rules
|
||||
|
||||
There are a few rules that the type system abides by and which one
|
||||
should know about when dealing with types in T.
|
||||
|
||||
#### Promotion
|
||||
|
||||
T has the concept of type promotion meaning that certain types when used
|
||||
in expressions with other *different* types will have some kind of
|
||||
automatic conversion take place.
|
||||
|
||||
Promotion takes place for integral types, below we have an example where
|
||||
a smaller type (`byte`) is automatically coerced to the bigger type (the
|
||||
`long`) when assigned to the variable of the type `long`:
|
||||
|
||||
``` d
|
||||
module simple_coerce_literal_good_stdalone_ass;
|
||||
|
||||
void function()
|
||||
{
|
||||
byte i = 1UL;
|
||||
long i1;
|
||||
|
||||
i1 = i;
|
||||
}
|
||||
```
|
||||
|
||||
This [example](TODO:%20add%20link) is available as part of the test
|
||||
suite.
|
||||
|
||||
#### Literals
|
||||
|
||||
There is one case whereby automatic conversion (known as *“coercion”*)
|
||||
is applied and that is with the usage of numeric literals. Firstly,
|
||||
however, we must discuss the default encoding scheme…. (TODO: do this)
|
||||
|
||||
TODO: Add information about how literals are ranged checked and then
|
||||
coercion applies (this is the **ONLY** case were coercion applies)
|
||||
|
||||
To-type \| Provided-type \|
|
||||
|
||||
1. TODO: Sign/zero extension
|
||||
- This is technically a code emit point to be made and can now be
|
||||
made eaisly due to `feature/universal_coercion` having
|
||||
`CastedValueInstruction` support
|
||||
2. Promotion?
|
||||
3. Precedence in interpretation when the first two don’t apply
|
||||
|
||||
What really happens:
|
||||
|
||||
> So far the smaller type is always promoted to the bigger type of the
|
||||
> two
|
||||
|
|
@ -1,73 +0,0 @@
|
|||
## Types
|
||||
|
||||
### Primitive data types
|
||||
|
||||
Primitive data type are the building blocks of which other more complex types are derived from. Each primitive type has the following 3 attributes:
|
||||
|
||||
1. **Type:** Indicates the name for the type
|
||||
2. **Width:** How many bits it takes up
|
||||
3. **Intended interpretation:** How it should be interpreted
|
||||
|
||||
#### Integral types
|
||||
|
||||
| Type | Width | Intended interpretation |
|
||||
|-----------|-------|---------------------------------|
|
||||
| `byte` | `8` | signed byte (two's complement) |
|
||||
| `ubyte` | `8` | unsigned byte |
|
||||
| `short` | `16` | signed short (two's complement) |
|
||||
| `ushort` | `16` | unsigned short |
|
||||
| `int` | `32` | signed int (two's complement) |
|
||||
| `uint` | `32` | unsigned int |
|
||||
| `long` | `64` | signed long (two's complement) |
|
||||
| `ulong` | `64` | unsigned long |
|
||||
|
||||
|
||||
#### Decimal
|
||||
|
||||
TODO: Add this
|
||||
|
||||
* float32, float64 etc
|
||||
|
||||
---
|
||||
|
||||
### Rules
|
||||
|
||||
There are a few rules that the type system abides by and which one should know about when dealing with types in T.
|
||||
|
||||
#### Promotion
|
||||
|
||||
T has the concept of type promotion meaning that certain types when used in expressions with other _different_ types will have some kind of automatic conversion take place.
|
||||
|
||||
Promotion takes place for integral types, below we have an example where a smaller type (`byte`) is automatically coerced to the bigger type (the `long`) when assigned to the variable of the type `long`:
|
||||
|
||||
```d
|
||||
module simple_coerce_literal_good_stdalone_ass;
|
||||
|
||||
void function()
|
||||
{
|
||||
byte i = 1UL;
|
||||
long i1;
|
||||
|
||||
i1 = i;
|
||||
}
|
||||
```
|
||||
|
||||
This [example](TODO: add link) is available as part of the test suite.
|
||||
|
||||
#### Literals
|
||||
|
||||
There is one case whereby automatic conversion (known as _"coercion"_) is applied and that is with the usage of numeric literals. Firstly, however, we must discuss the default encoding scheme.... (TODO: do this)
|
||||
|
||||
TODO: Add information about how literals are ranged checked and then coercion applies (this is the **ONLY** case were coercion applies)
|
||||
|
||||
| To-type | Provided-type |
|
||||
|
||||
1. TODO: Sign/zero extension
|
||||
* This is technically a code emit point to be made and can now be made eaisly due to `feature/universal_coercion` having `CastedValueInstruction` support
|
||||
2. Promotion?
|
||||
3. Precedence in interpretation when the first two don't apply
|
||||
|
||||
|
||||
What really happens:
|
||||
|
||||
> So far the smaller type is always promoted to the bigger type of the two
|
||||
Loading…
Reference in New Issue