Skip to content

Commit

Permalink
Remove fixed array faking not support message
Browse files Browse the repository at this point in the history
  • Loading branch information
ChAoSUnItY committed May 13, 2022
1 parent 1b1e001 commit aedfce1
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,16 +81,16 @@ df.add_type<string>('your unit', 'your faking function's name') ?
## Supported Data Types

Vaker supports:
`[]T`, `map[K]V`, `string`, `rune`, `bool`, `i8`, `i16`,
`[]T`, `T[]! (Sized array)`, `map[K]V`, `string`, `rune`, `bool`, `i8`, `i16`,
`int`, `i64`, `byte`, `u16`, `u32`, `u64`, `f32`, `f64`, `struct`, `time.Time`

**while:**
***every type symbols: T, K, V, isn't interface or sized array (Unstable for now)***
***every type symbols: T, K, V, isn't interface***

Additionally, Vaker supports embedded structure, or nested struct data faking.

Vaker does not support faking:
`interface`, `T[]! (Sized array)`
`interface`

See [Limitations](#limitations)

Expand Down Expand Up @@ -166,7 +166,6 @@ Vaker generates faking functions at compile time, so it spend more memory/time o
## Limitations

1. Vaker does not support faking interface, since interface in V cannot be implemented in runtime.
2. Vaker does not support faking sized array, since V's compile-time reflection cannot assume whether array is sized or not, which leads not unknown size of array <br/> <b> Update: It's confirmed that this limitation is not really a **limitation** but a *V Lang compiler bug*, I will keep tracking this until the bug is fixed, see https://github.com/vlang/v/issues/13632 </b>

## Contribution

Expand Down

0 comments on commit aedfce1

Please sign in to comment.