assembler/src/reports, branch v2.3.0Rust library for parsing assembly languageshttps://code.benbridle.com/assembler/atom?h=v2.3.02025-04-27T00:38:40ZReplace ansi library with inked library2025-04-27T00:38:40ZBen Bridleben@derelict.engineering2025-04-27T00:38:40Zurn:sha1:c13c1f2748598343e01128c3f734df309aa4a26d
The inked library handles colours correctly on Windows. The log library
has also been updated to the newer version which uses inked internally.
Don't print original source in redefinition errors2025-03-24T21:59:30ZBen Bridleben@derelict.engineering2025-03-24T21:59:30Zurn:sha1:34ca33d86fd47ca912751bd8578e66f449639a7c
The source context of the original definition of a redefined symbol was
being printed when reporting a redefinition error. Since only the
source code containing the redefinition was available, if the original
definition was in a different file then the source context of the
original definition would just pull from this source code and the
context shown would be completely nonsensical.
Large restructure2025-03-17T22:50:29ZBen Bridleben@derelict.engineering2025-03-17T22:50:19Zurn:sha1:f8a694267d3981b0437c05fc248406116ea9ec06
Files were moved to be better organised, error messages were changed to
be more general, and a Compiler type was added to the library.
Implement source chains2025-03-11T03:18:01ZBen Bridleben@derelict.engineering2025-03-11T03:18:01Zurn:sha1:a9e9dd452e23fa2e816df926a56c1f743eb32488
A SourceSpan can now contain a child SourceSpan, ad infinitum, in order
to represent a chain of locations. The report_source_issue function
has been changed to print the entire chain, instead of just one
SourceSpan.
The report_source_issue function has also been changed to correctly
print SourceSpans that extend across multiple source lines.
Make output of report_source_issue more concise2025-03-10T03:31:06ZBen Bridleben@derelict.engineering2025-03-10T03:31:06Zurn:sha1:6fb6f2836232fe78dce507fa899629bbefb7b449
Instead of displaying two locations for the same error, only show the
in_merged source location if there is no in_source location.
Create struct for reporting unused definitions2025-02-13T07:23:25ZBen Bridlebridle.benjamin@gmail.com2025-02-13T07:23:25Zurn:sha1:e717e32badebcd34f590e1e58d6417ebf8c8d973Create struct for reporting in detail the symbols in a resolver2025-02-09T23:57:52ZBen Bridlebridle.benjamin@gmail.com2025-02-09T23:57:52Zurn:sha1:6ceec5361c80b466f4a2a3719efb09ad6d6efa99
This is used for debugging symbol definition and resolution issues.
Track related symbols in resolver2025-02-09T23:44:42ZBen Bridlebridle.benjamin@gmail.com2025-02-09T23:42:33Zurn:sha1:8ddf72ad0252f17913540a2e767966899a29d1b6
As well as the already-implemented tracking of the existing definition
of redefinitions, the resolver will now also track the definition that
resolves each reference, and the references resolved by each definition.
Instead of using tuples to hold this information, named wrapper structs
have been created for each category.
Import from the log and ansi crates once in the reports module2025-02-09T23:37:16ZBen Bridlebridle.benjamin@gmail.com2025-02-09T23:37:16Zurn:sha1:1c9e795245c5da0ea896a4824fb41c9542857ecc
This is tidier than duplicate imports in every file of the module.
Simplify infallible indexing operations in resolver2025-02-09T23:34:56ZBen Bridlebridle.benjamin@gmail.com2025-02-09T23:34:56Zurn:sha1:dedd999b8f923641dce512c21db5528d32356cc6
Indexing into a resolver with a pointer from the same resolver should
never fail, and if it does we don't want to silently squash the error.