-
-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# track, Hyper-optimized Telemetry exercise - unclear instructions #2160
Comments
Hello. Thanks for opening an issue on Exercism. We are currently in a phase of our journey where we have paused community contributions to allow us to take a breather and redesign our community model. You can learn more in this blog post. As such, all issues and PRs in this repository are being automatically closed. That doesn't mean we're not interested in your ideas, or that if you're stuck on something we don't want to help. The best place to discuss things is with our community on the Exercism Community Forum. You can use this link to copy this into a new topic there. Note: If this issue has been pre-approved, please link back to this issue on the forum thread and a maintainer or staff member will reopen it. |
Do you perhaps have a better suggestion for how to handle this? |
As I understood the task, the only valid values of the prefix byte are these:
If that's correct it means that if any of 2, 4, 8, 248, 252 or 254 is passed as a prefix byte to
instead of this Or perhaps it can be removed completely. Or it may be less specific, like |
I like that! Would you be willing to submit a PR? |
Took me a while to get back to it, sorry. Here's the PR #2163. |
@ErikSchierboom The PR has been merged, I think this issue can be closed. |
Hello,
In the Hyper-optimized Telemetry exercise of the C# track the last paragraph seems to give vague sentence which contradicts the task.
Here's the exercise
The last paragraph goes like this:
In the last sentence it says that if the prefix byte is not one of -8, -4, -2, 2 or 4 then 0 should be returned. But at the same time in the example above it has the prefix byte 0xFC, which is 252, which is none of the numbers listed in the last sentence, and the returned type is expected to be 2147483647 which contradicts the 0 from the last sentence.
So this last sentence - what is it supposed to mean? Perhaps it needs to re-phrased to make it more clear for the reader.
Thanks!
The text was updated successfully, but these errors were encountered: