Skip to content

bump yaxpeax-arch version#11

Closed
Ravenslofty wants to merge 2 commits into
no-gods-no-from
lofty/yaxpeax-arch-0.3
Closed

bump yaxpeax-arch version#11
Ravenslofty wants to merge 2 commits into
no-gods-no-from
lofty/yaxpeax-arch-0.3

Conversation

@Ravenslofty
Copy link
Copy Markdown
Collaborator

I mean, yaxpeax-arch 0.3 is over a year old,,,

@Ravenslofty Ravenslofty requested a review from iximeow September 1, 2025 17:28
@Ravenslofty
Copy link
Copy Markdown
Collaborator Author

I guess since this is a semver-breaking change, this implies a 0.3.0 release needed.

@iximeow
Copy link
Copy Markdown
Owner

iximeow commented Sep 29, 2025

hmmm 0.3.0 also means it's probably easier to do interesting syntax highlighting for ia64 instructions, nice. super fair to bump this along.

@iximeow
Copy link
Copy Markdown
Owner

iximeow commented Sep 29, 2025

it turns out if you don't depend on tap = "1.0.1", bitvec 1.x will produce some kinda gnarly macro errors at compile time (would be fixed by ferrilab/bitvec#301)

i'd rather not have the one-off dependency here to fix bitvec 1.x and i don't see anything pressing to move off of 0.19 (other than old), so i'll keep an eye on that PR and include a914740 if/when the time comes. other than that, i've pulled in the yaxpeax-arch 0.3.0 bump, and before publishing an 0.3.0 i figure i'll add some fuzz tests here too. thanks!

@iximeow iximeow closed this Sep 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants