C# track, Hyper-optimized Telemetry exercise - unclear instructions about csharp HOT 6 CLOSED

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.

from csharp.

So this last sentence - what is it supposed to mean? Perhaps it needs to re-phrased to make it more clear for the reader.

Do you perhaps have a better suggestion for how to handle this?

from csharp.

As I understood the task, the only valid values of the prefix byte are these:

• for signed short: 254
• for unsigned short: 2
• for signed int: 252
• for unsigned int: 4
• for signed long: 248
• for unsigned long: 8.

If that's correct it means that if any of 2, 4, 8, 248, 252 or 254 is passed as a prefix byte to TelemetryBuffer.FromBuffer method then the method will return correct numeric value. If the prefix byte is none of these six values, then the method will return 0. If what I just said is correct then shouldn't the last sentence say this:

If the prefix byte is not one of 2, 4, 8, 248, 252 or 254 then 0 should be returned.

instead of this If the prefix byte is not one of -8, -4, -2, 2 or 4 then 0 should be returned.?

Or perhaps it can be removed completely. Or it may be less specific, like If the prefix byte is of unexpected value then 0 should be returned.

from csharp.

If the prefix byte is of unexpected value then 0 should be returned.

I like that! Would you be willing to submit a PR?

from csharp.

Took me a while to get back to it, sorry. Here's the PR #2163.

from csharp.

@ErikSchierboom The PR has been merged, I think this issue can be closed.

from csharp.