assembler, branch mainRust library for parsing assembly languageshttps://code.benbridle.com/assembler/atom?h=main2025-04-27T00:39:01ZUpdate version to 2.3.02025-04-27T00:39:01ZBen Bridleben@derelict.engineering2025-04-27T00:39:01Zurn:sha1:a9640fce1aaa5e80170ce4d2ac700f66cfffbb4bReplace 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.
Update vagabond library2025-04-15T01:23:04ZBen Bridlebridle.benjamin@gmail.com2025-04-15T01:18:08Zurn:sha1:55e64d35273a425b52b7d913b9368af2f0370bbb
The latest version 1.1.1 of vagabond removes all nightly features,
which will allow all projects using the assembler library to compile
on stable Rust once the extract_if feature is stabilised.
Update version to 2.2.22025-04-01T04:15:46ZBen Bridleben@derelict.engineering2025-04-01T04:15:46Zurn:sha1:85c1fd299e04e27307a1c1633282df6f1d579a98Report all symbols involved in a cyclic dependency error2025-04-01T04:15:31ZBen Bridleben@derelict.engineering2025-04-01T04:15:31Zurn:sha1:1400c0cc3bdd7f685d63fe174286dd106337e735
Without this, it's difficult to sort out a cyclic dependency error when
many large source files are involved.
Fix resolver error2025-04-01T04:12:05ZBen Bridleben@derelict.engineering2025-04-01T04:10:51Zurn:sha1:1cc0269f75b8b2dd979c01ef4a500a09a0cc4354
To check if a particular definition was defining a particular symbol,
the names of the definition and reference were being compared, when the
namespace-aware Symbol::defines method should have been used instead.
This was causing an issue where a namespaced definition would be marked
as resolving a with the same name in a different namespace. This was
resulting in a very complicated and incorrect cyclic dependency error.
Tidy source code2025-04-01T04:08:03ZBen Bridleben@derelict.engineering2025-04-01T04:07:49Zurn:sha1:5253be190b1cac16fe4f8658491959e15e52f1b3Update version to 2.2.12025-03-24T22:00:22ZBen Bridleben@derelict.engineering2025-03-24T22:00:22Zurn:sha1:648151b7684214a86e894d0ca813d7a89317722cDon'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.
Update version to 2.2.02025-03-17T23:03:59ZBen Bridleben@derelict.engineering2025-03-17T22:49:12Zurn:sha1:24080dd75092ea5ef8c10fd179aa28b8db534c7f