vlang parser in zig
Find a file
2019-08-27 11:54:21 -03:00
examples parser: simplify finishAssignment, add StarEqual support 2019-08-27 11:54:21 -03:00
src parser: simplify finishAssignment, add StarEqual support 2019-08-27 11:54:21 -03:00
.gitignore initial commit 2019-06-03 21:29:53 -03:00
build.zig build.zig: s/spoodle/vig 2019-08-26 13:39:00 -03:00
LICENSE add LICENSE 2019-06-03 21:31:08 -03:00
README.md readme: move error handling to sub-objectives of a type system 2019-08-26 22:44:36 -03:00

vig

a v parser in zig, also a shitpost taken too far

(will likely be done as a full compiler, who knows, leave a like and subscribe for more epic adventures)

why

  • because i want to learn parsers and what best to do it with a language i'm negatively charged towards
  • theres an ast now it looks pretty
  • i finally understand recursive descent parsers

variations

  • for is split between for and loop because my fucking god i cant stand having four different variations of for to parse.

  • struct initialization is with Struct.{}, not Struct{}, to remove parsing ambiguities (if a {} and a{}, v solves that with case, e.g structs Must Be Properly Titled and i can't bother with that)

  • function parameters must have a type always

  • ifs are always statements, not expressions (can't use if as an r-value)

  • no ++, --

  • no match

  • no embedded structs

  • no v orm

  • no codegen

  • no inline assembly

wip

  • +=, -=, and the rest of the gang
  • no for yet
  • no arrays yet
  • no map yet
  • no in yet (probably will be dropped)
  • no module, import yet
  • no interfaces yet
  • no enums yet
  • no generics yet
  • no attributes yet ([live], [skip])
  • no defer yet
  • no operator overloading methods yet
  • do we really want a type system (optionals included)
    • no error handling yet (call() or {blah})
    • no ? postfix operator yet (call()?)
  • do we really want to output c
  • do we really want to output llvm
  • do we really want to output x86

how