yaxpeax-arch - shared traits and definitions for yaxpeax decoders

Age	Commit message (Collapse)	Author
2021-07-03	reader impls for various word sizes	iximeow

2021-07-03	add a Reader type that can read architecture-defined words	iximeow
	this is useful for instruction sets like arm where instructions are guaranteed to be 4 bytes, as well as instruction sets where an instruction word is not a multiple of u8 bytes.
2021-07-03	define a standard decode error for client libraries to use	iximeow
	additional variants will require clients to implement DecodeError, still
2021-06-14	address diff is an u64 thingy that can be added to addressesnonbyte-words	iximeow

2021-06-14	experiment	iximeow

2021-05-07	swap termion dep for crossterm, simplify Colorization interfaces0.0.5	iximeow

2020-05-03	add AddressDiff, CHANGELOG, and bump to 0.0.40.0.4	iximeow

2020-01-20	Default impl of ColorSettings was needlessly feature gated	iximeow
	on a feature that doesnt exist, no less!
2020-01-18	finally replace `stringy` with something usable	iximeow
	addresses must implement a function that returns a struct that is applicably formattable. particularly because the default Display impl on primitives is not necessarily desirable, if you want hex. additionally this allows meaningful Display for complex (eg, not a single primitive) addresses, such as segmented memory also expose AddressDisplay to name outside this crate. what an oversight
2020-01-15	no_std!!	iximeow
	this makes yaxpeax-arch no_std. generally nothing has changed w.r.t downstream crates, but a lot to do with colorization has been moved tweaked to make it no_std-friendly (specifically, allowing `termion` to be an optional dependency) this also makes address parsing optional, in the hopes that decode-only use cases don't need to involve as much machinery when building.
2020-01-13	default Decoder::decode() impl	iximeow

2020-01-12	allow for granular and customizable errors when decoding instructions	iximeow

2020-01-12	color helper for misc instructions	iximeow

2020-01-12	decoders are stateful, so decode functions should take them as a parameter	iximeow

2020-01-12	warnings-b-gone	iximeow

2020-01-12	addresses are Hash	iximeow

2020-01-12	remove unused import	iximeow

2020-01-12	sneak hash/partialeq/etc into yaxpeax-arch	iximeow

2020-01-12	awful tweaks to expose a serde flag on yaxpeax-arch which will trickle ↵	iximeow
	through everything
2020-01-12	add color for program counter register (default to the same as ret and friends)	iximeow

2020-01-12	expose platform op color	iximeow

2020-01-12	fix sign display bug	iximeow

2020-01-12	add some display logic into arch	iximeow

2020-01-12	tweak how ColorSettings is used	iximeow
	enum to tie together a color and a thing to be colored, helper methods to build that, and an impl on Option that gives non-colored variants
2020-01-12	add many more color types to settings, AddrParse to parse addresses from hex ↵	iximeow
	or decimal strings
2020-01-12	real color settings, and defaults	iximeow

2020-01-12	add traits for syntax highlighting and contextualized display	iximeow
	these traits are not ideal but are what i can do in rust right now the initial attempt to add these traits involved a trait providing a `colorize` function that returned a struct (or tuple) that impl'd Display but bundled all useful data together. this would be nice because use would be like: ``` println!("the next instruction is: {}", instr.colorize(settings)); ``` but this runs into the same kind of lifetime issues as mentioned in the ContextRead commit. additionally complicating is contextualization, which involves a larger structure than just a copyable color setting - a similar builder-and-display style use would be nice but involves a third lifetime (the content, the colors, the contexts) and is not workable. references could be Rc pointers and this all might work. why not do that? moral opposition to cloning Rc pointers when doing any instruction rendering. might be worth revisiting later if i'm convinced this is too annoying - it's already close. meanwhile, it turns out implementing traits on tuples is currently not possible anyway - tuples are not #[fundamental]. in the future i need to investigate if i can use macros to tie into `derive`, so that a ShowContextual impl can #[derive(Colorize, Display)]. those implementations would really just call ShowContextual.colorize with fewer and fewer parameters non-None. the blanket impl ``` impl <T, U> Colorize for T where T: ShowContextual<U> ``` is entirely just a relic of one attempt, and can be ignored. this idea conflicted with coherence rules because someone else could impl Colorize for some type covered under this blanket impl.
2020-01-12	add impls for address as used by x86_64	iximeow

2020-01-12	tweak core lifetimes, add an address formatter	iximeow

2020-01-12	require Arch to have addresses that can += and -=, as well as that ↵	iximeow
	instructions have a debug display
2020-01-12	add some predetermined address display stuff	iximeow
	also add zero and one traits to Address, adjust layout
2020-01-12	base definition of an arch to yaxpeax	iximeow