Can you give me half?
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.
dc, 3 unique bytes, 138 bytes …
2y ago
[C (gcc)], 8 7 unique c …
2y ago
Ruby, 7 unique, 12 bytes `$ …
2y ago
Embed ESCR, 6 unique character …
2y ago
[Python 3], 5 unique bytes, 28 …
2y ago
Clojure - 15 characters total, …
2y ago
Perl, 3 distinct, 12 bytes …
2y ago
J, 4 3 distinct, 6 bytes `` …
2y ago
[Python 3], 7 distinct charact …
2y ago
Lua 5.4, 3 unique characters …
2y ago
J, 4 unique, 4 char ``` -: …
2y ago
[Julia 1.0], 16 bytes …
2y ago
Ruby, 10 distinct, 35 chars ` …
2y ago
Raku (also Perl polyglot), 5 u …
2y ago
Scala, 15 bytes ```scala '#' …
2y ago
Japt, 1 byte ½ Test …
2y ago
Javascript, 5 Distinct charact …
2y ago
JS, 15 bytes `!![]/(-[]-[]) …
2y ago
[Extended] Dyalog APL, 4 bytes …
9mo ago
Golfscript, 8 6 bytes, 5 uniqu …
1y ago
Vyxal, 1 byte ``` . ``` Tr …
1y ago
Fig, 2 unique, 2 total ``` H …
1y ago
MATL, 3 distinct, 3 total ``` …
2y ago
23 answers
[Extended] Dyalog APL, 4 bytes*
*10 bytes, 4 unique
'÷'÷⍥≢'÷÷'
This computes the length of the string '÷' divided by the length of the string '÷÷'
Alternate solution (extended only) (6 unique, 6 bytes)
⊢÷+⍨×∞
This computes
\[ \left(\lambda x.\frac{x}{x+x}\right) \mathrm{sign}\infty \]
0 comment threads
Fig, 2 unique, 2 total
H!
Halves the negation of the empty string when no input is given.
0 comment threads
C (gcc), 8 7 unique
cos(cos-cos)/(cos(cos-cos)-(-cos(cos-cos)))-1 unique character thanks to @orthoplex
Lua 5.4, 3 unique characters
#'#'/#'##'
[...] scoring is done in terms of number of unique characters used in the submission.
- Hashtag #
- Single quote '
- Slash /
0 comment threads
Python 3, 5 unique bytes, 28 total
(()==())/((()==())+(()==()))
(, ), =, /, +
Uses (()==()) to get True with only 3 unique characters, as well as making the later grouping of (...+...) free.
0 comment threads
Clojure - 15 characters total, 5 unique
Inspired by the Embed ESCR solution above, I realized I could do something very similar in Clojure:
(/(*)(+(*)(*)))
This returns 1/2, which is a Ratio in Clojure.
(*) - * with no arguments returns 1.
(+...) - + returns the sum of its arguments
(/...) - / divides the first argument by the second, returning a Ratio.
0 comment threads
Perl, 3 distinct, 12 bytes
s//yy//y/y//
Prepends yy to the start of $_, and then transliterates them, dividing the count of each.
0 comment threads
J, 4 3 distinct, 6 bytes
-:_-:_
Half of _ -: _ which is asks if infinity matches infinity. Thanks to @xash in the APL farm discord for saving the 3 unique bytes and orthoplex for catching my blunder.
JS, 15 bytes
!![]/(-~[]-~[])
Basically typed random characters into js console and it worked.
Ruby, 10 distinct, 35 chars
t=/%/=~%/=%/
o=/%/=~%/==%/
t/o.to_f
0 comment threads
Scala, 15 bytes
'#'.toFloat/'F'
Characters in Scala kinda get casted to integers. This is usually annoying, but it's useful when golfing. # is 35 and F is 70, and the .toFloat prevents it from doing integer division and truncating to 0.
0 comment threads
Embed ESCR, 6 unique characters, 19 bytes
[/ [*] [+ [*] [*]]]
Each [] pair of brackets encloses an in-line function. The first token in a function is the function name, and subsequent tokens, if any, the parameters. Functions can be nested.
The * function multiplies a series of numbers. The product is initialized to 1 before the first term. A side-effect is that just "*" without any parameter returns 1. The "+" function adds two 1s to make 2. The "/" function divides the first parameter by the second, so 1 divided by 2. The result is 1/2.
The spaces are enforced for readability, and to simplify the parsing rules. This NOT a golfing language.
Japt, 1 byte
½
Jelly, Vyxal, 1 byte
.
Yeah, golf langs still kind of kill this challenge.
2 comment threads