Skip to content

2.0.0

Compare
Choose a tag to compare
@AndrewRayCode AndrewRayCode released this 22 Jul 20:54
· 72 commits to main since this release
1f51744

Introduced in this PR.

This is a significant set of changes, some breaking.

The main goal of this change is to support tracking whether or not functions and types have declarations in the scope. The type and function scope entries now have a definition key, which points to the definition of a function or type.

Features:

  • The parser now supports overloaded function tracking in scope. A function scope index went from { [fnName]: { references: AstNode[] } to { [fnName]: { [overloadSignature]: { declaration?: AstNode, references: AstNode[], ... } } }. This is a breaking change. Note that if you're using the renameFunctions utility function provided by the parser, this change may be opaque to you.
  • The semantic analysis of this library is still mostly non-existent, but there are now improved warnings for missing function and type definitions
  • New failOnWarn parser option flag to raise errors on things like undefined variables.

Breaking API changes:

  • Adds a new TypeNameNode AST node type, to distinguish a type name from an identifier in the AST. If you're using node visitors to visit identifier nodes, you'll need a new visitor for type_name nodes.
  • Removes ParameterDeclaratorNode and moves everything into ParameterDeclarationNode
  • In the AST node Typescript definitions, any time I didn't know what node was, I put in any. I replaced that with AstNode. I don't yet know if I want to keep this, because AstNode could lead to more issues than it causes. It could lead to type errors and forced casting that wouldn't come along with any. Like it might force you to make sure our node isn't a LiteralNode even though technically the grammar doesn't allow for that.
  • Previously, a scope binding (aka a variable declaration use), had the type { initializer: declaration_ast_node, references: [ast_node, ...] }, where the ast_node could be the declaration node containing the identifier. It turns out initializer was never part of the Typescript type, so you might never have seen it. Either way, initializer is renamed to declaration, and it now points to the identifier node rather than the declaration.

Internal development:

  • All of the functions that were defined in src/parser/glsl-grammar.pegjs are now rewritten in typescript and extracted into an external file.
  • Various clean-ups of the grammar, like removing the duplicate path function_prototype_no_new_scope
  • Cleanup of tsconfig.json file
  • Adds the tracer Peggyjs option to the parser, for debugging
  • Removes preprocessor tests from parse.ast.ts
  • Breaking out of source code into more logical files