Skip to content

Improve internal error handling #19

@ToxicFrog

Description

@ToxicFrog

At the moment, error handling is kind of a dog's breakfast of error() and assert() calls. Users can easily end up seeing a stack trace from vstruct internals.

This isn't terribly hard to fix:

  • internal functions for internal, external, hard, and soft errors
  • API functions should pcall the implementation
  • turn error objects into appropriate throws or returns, including the internal stack trace if appropriate

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions