Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Meta

Post History

60%
+1 −0
Meta Codidact Fractional Byte Consensus

Over on the Code Golf StackExchange site, there is a meta consensus that answers can be scored in fractional bytes if there exists such an encoding method. So, to quote the linked consensus questi...

1 answer  ·  posted 11mo ago by lyxal‭  ·  last activity 11mo ago by WheatWizard‭

Question discussion
#1: Initial revision by user avatar lyxal‭ · 2023-06-20T02:22:31Z (11 months ago)
Codidact Fractional Byte Consensus
Over on the Code Golf StackExchange site, there is a [meta consensus](https://codegolf.meta.stackexchange.com/questions/24251/what-is-our-consensus-for-fractional-byte-functions) that answers can be scored in fractional bytes if there exists such an encoding method.

So, to quote the linked consensus question:

> For languages with fractional byte code pages, such as half-byte code pages or huffman coding, should functions be allowed to be submitted without padding to a whole number of bytes?

<sup>This came up when I went to write [this answer](https://codegolf.codidact.com/posts/288535/288546#answer-288546) and then realised "hang on there's no consensus about fracbytes here yet"</sup>