Timeline for I want 8 bits for every character!
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2022 at 19:56 | comment | added | emanresu A | Fixed, I think. | |
| May 23, 2022 at 19:55 | history | rollback | emanresu A | Rollback to Revision 1 | |
| May 23, 2022 at 17:12 | comment | added | Jonathan Allan | The reason this does not work for test case 3 is that the encoded data does not end with exactly one "byte" of zeros. This, I believe, is a result of the linked (reverse) challenge having the specification "If the last byte is not 8 bits long, add zeros at the end till it is 8 bits long". Thus converting from base 256 loses the information of how many of the implicit zeros are leading vs trailing. | |
| May 23, 2022 at 10:49 | comment | added | Kevin Cruijssen | Hmm.. the longest test case seems to fail as well for some reason. | |
| May 23, 2022 at 10:07 | history | edited | emanresu A | CC BY-SA 4.0 | added 63 characters in body |
| May 23, 2022 at 10:03 | comment | added | emanresu A | @KevinCruijssen Oh oops... that's happening because I forgot to deal with zeroes. | |
| May 23, 2022 at 10:01 | comment | added | Kevin Cruijssen | Your result sometimes contains a trailing space? Your current test case contains a trailing space for example. And "6932", [137,147,16] contains a trailing space as well. (But not all of them do, because "a", [255] lacks that trailing space.) | |
| May 23, 2022 at 0:20 | history | edited | emanresu A | CC BY-SA 4.0 | added 77 characters in body |
| May 23, 2022 at 0:14 | history | rollback | emanresu A | Rollback to Revision 1 | |
| May 23, 2022 at 0:13 | history | edited | emanresu A | CC BY-SA 4.0 | added 109 characters in body |
| May 23, 2022 at 0:02 | history | answered | emanresu A | CC BY-SA 4.0 |