Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
generate random UUIDs

UUID

Returns a random v4 UUID of the form xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx, where each x is replaced with a random hexadecimal digit from 0 to f, and y is replaced with a random hexadecimal digit from 8 to b.

There's also @LeverOne's approach using iteration, which is one byte shorter.

function b(
a // placeholder
){
return a // if the placeholder was passed, return
? ( // a random number from 0 to 15
a ^ // unless b is 8,
Math.random() // in which case
* 16 // a random number from
>> a/4 // 8 to 11
).toString(16) // in hexadecimal
: ( // or otherwise a concatenated string:
[1e7] + // 10000000 +
-1e3 + // -1000 +
-4e3 + // -4000 +
-8e3 + // -80000000 +
-1e11 // -100000000000,
).replace( // replacing
/[018]/g, // zeroes, ones, and eights with
b // random hex digits
)
}
function b(a){return a?(a^Math.random()*16>>a/4).toString(16):([1e7]+-1e3+-4e3+-8e3+-1e11).replace(/[018]/g,b)}
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004
Copyright (C) 2011 Jed Schmidt <http://jed.is>
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. You just DO WHAT THE FUCK YOU WANT TO.
{
"name": "UUID",
"description": "Generates random UUIDs",
"keywords": [
"UUID",
"ID",
"random"
]
}
@phyreman
Copy link

@RobertoMachorro Just ensuring the random numbers come from a crypto source instead of Math.random(). It's definitely slower than molasses though, lol. I think the OP stopped once it hit the point of basically not being able to golf it much more and a spec-compliant version was posted.

@Oman395
Copy link

Oman395 commented Nov 3, 2021

Ok I don't even know how, but I typed in 'var konami' with github copilot and it gave me:

var konami = { // https://gist.github.com/jed/982883
    "up": false,
    "down": false,
    "left": false,
    "right": false,
    "b": false,
    "a": false,
    "start": false,
}

how

@getify
Copy link

getify commented Feb 9, 2022

Can anyone explain the reasoning behind what seems rather arbitrary, in the replacing only 0s, 1s, and 8s with random hex digits, and not, for example, replacing all numbers with such digits? I'm sure I missed some detail that explains it.

@jed
Copy link
Author

jed commented Feb 9, 2022

IIRC the spec requires those digits to be certain values.

@getify
Copy link

getify commented Feb 9, 2022

@jed thanks for the link. I browsed through that spec to see if I could find something that jumps out. I see lots of discussion of bits in fields and such, but nothing that obviously connects digits 0, 1, and 8 to needing to be replaced. In fact, the part you linked to specifically says:

Set all the other bits to randomly (or pseudo-randomly) chosen values.

In any case, appreciate having further info. My understanding is still incomplete, but it's less incomplete now. ;-)

@getify
Copy link

getify commented Feb 9, 2022

Oh, wait... I think I maybe get more of it now... the code has stuff like 1e3 and 8e3, which are like 1000 and 8000... but it also has 4e3... so basically it's targeting all the 1s, 0s, and 8s for replacement, but leaving the 4 in the middle alone.

@jed
Copy link
Author

jed commented Feb 9, 2022

That's because it's not part of the spec, it's part of the genius of @subzey. Look at the string that's being replaced

  • 0 and 1 (1 is used as the head of a segment to prevent truncation),
  • 8, which is special cased with the ^ operation to clamp it to the proper values, but not
  • 4, which cannot be replaced because it specifies the version in the spec.

@jed
Copy link
Author

jed commented Feb 9, 2022

right, you got it. the 1 could be any other digit, really, it's just a placeholder, but the 8 was selected for its bitwise operation properties.

@jed
Copy link
Author

jed commented Feb 9, 2022

(there's a walkthrough here, fwiw)

@getify
Copy link

getify commented Feb 9, 2022

@jed thanks! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment