5 Commits

Author	SHA1	Message	Date
Parnic	483f1f2502	Strip more BOMs ... The 01a sample text file I created in VS2022 has a big-endian utf-16 byte order mark in front. When read with File.Read* methods it was fine, but when piped in from the command line it was causing the integer parsing to fail due to the extra bytes on the front. This is the cleanest way I can find to strip any of a set of BOMs from a string. Maybe there's an easier way somewhere, but the main issue is that using something like line[0..1].SequenceEqual() may or may not use wide chars (0xFEFF as opposed to 0xFE, 0xFF, for example) so I can't just build a list of preamble arrays and check if the byte version of the string starts with them. The "StripPreamble" character list is still a mystery. I found it while working on my Macbook for aoc2021 and can't seem to find any search results indicating what these bytes represent, so...just gonna leave it there.	2022-12-01 11:59:43 -06:00
Parnic	756d8e519a	Don't process twice if the file exists on disk	2022-11-30 20:40:00 -06:00
Parnic	22c89a7e0e	Apply a few more Rider suggestions	2022-11-30 20:38:03 -06:00
Parnic	55f8a1806c	Embed inputs as resources ... This enables the binary to be invoked from anywhere and still run on the default input set, as well as being more portable/shareable which can help with performance comparisons between machines. Files are still supported if they exist.	2022-11-30 20:37:36 -06:00
Parnic	23945154d4	Initial commit - framework	2022-11-30 17:19:53 -06:00