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 »
Challenges

Comments on Can you give me half?

Post

Can you give me half?

+11
−0

Challenge idea taken from: Eliseo D'Annunzio

Task

Provide code that evaluates to 0.5 numerically, i.e. the output must be recognized by your chosen language as a numeric value (Number, float, double, etc), not as a string.

The catch, the characters 0 through to 9 cannot be used.

One example that fits the brief would be the following:

((++[[]][[~~""]]<<++[[]][[~~""]]))**((--[[]][[~~""]])) which works out to 0.5 in JavaScript.

Scoring

This is a code challenge, where scoring is done in terms of number of unique characters used in the submission. Ties are broken by lowest bytecount.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Languages without built in float (2 comments)
Leaderboard scores (1 comment)
Leaderboard scores
trichoplax‭ wrote over 1 year ago

I notice that several of the answers show on the leaderboard with their byte count instead of the number of unique characters, which often gives them a significantly higher (worse) score. In many cases this is because the answer heading shows the unique characters and the byte count, and the leaderboard script picks up the last number in the heading. Listing the byte count first, followed by the number of unique characters, would result in a correct leaderboard.

Is it worth adding a note about this to the Scoring section, as answers are still coming in?

We could also then suggest edits on the answers that are being misrepresented on the leaderboard, to switch the order of the heading.