WerWolv / WerWolv/PatternLanguage
Template parameters (and locals) are unintuitively affected by endianness
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 275
- Forks
- 75
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 10
Description
import std.io;
struct Test<auto t> {
std::print("{}", t);
u32 a = t;
};
le Test<5> test1;
be Test<5> test2;
std::print("{} {}",test1,test2);
results in:
I: 5
I: 5
I: bitfield Test { a = 5, t = 5 } bitfield Test { a = 83886080, t = 6646139978924579364519035301401722880 }
Inside the template, the parameter is read the same way (both being 5). This works as expected and allows consistent used for e.g. bitfield lengths.
However, the endianness seems to take effect when reading the template parameters (and locals) from outside the template. This makes it difficult to determine what they were, such as from a format function
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce issue #119 with the shown little-endian and big-endian Test instances, then trace how template parameters and locals are read inside and outside the template. The fix is done when formatting or otherwise reading those values externally preserves the value observed inside the template for both endiannesses, without breaking the existing bitfield-length behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100