Christoffer Lerno

1. Implement the pattern matching, presumably single wildcard is ok? See PathMatchSpec() 2. Optionally recursive 3. Optionally relative paths 4. Optionally rebase paths on new directory

Compile time string functions

1

In order to facilitate certain types of macros, the following macros could be built in: - [x] `@str_to_upper(#f)` Convert string to upper case. - [x] `@str_to_lower(#f)` Convert string to lower...

```c // Supporting the full set. macro Foo._slice(Foo* foo, a, b, $a_from_end, $b_from_end) { $if ($a_from_end) $if ($b_from_end) return foo.values[^a..^b]; $endif return foo.values[^a..b]; $endif $if ($b_from_end) return foo.values[a..^b]; $endif return...

Support float128

1

Support the float128 type: 1. Support max/min for float128 2. Allow compile time folding of float128

LLVM 15 was recently released. Would you consider adding LLVM 14 and 15?

Added some tiny code (not used!) in the examples to show how they would change if defer.

Make it easier to find out about array and map literals

1

The initial parts of the current overview documentation deals with literals: https://odin-lang.org/docs/overview/#lexical-elements-and-literals However, this section only mentions characters and numbers. It does not mention array literals, which are only implicitly...

Should it be possible to splat normal arguments?

4

```c fn void foo(int x, int y) { ... } fn void foo2(int x, int...) { ... } fn void main() { int[2] a = { 1, 2 }; foo2(1,...

Create functions from c3c to manipulate the project.json

9

Yes, it's straightforward to edit the project.json, but the downside is that it's currently actually json5. Plus there is some need to consult the documentation just to do simple things,...

Test folder should be included when selecting "test"

2

The project has a "test" folder by default. So the expectation (and intention!) is that this folder should be picked up when doing `c3c test`. This does not seem to...