# MOLD and LOAD parity

**URL:** <https://revolt.metaeducation.com/forum/t/mold-and-load-parity/1429>\
**Category:** Semantics\
**Created:** [December 10, 2020, 11:00pm UTC](https://revolt.metaeducation.com/forum/t/mold-and-load-parity/1429 "2020-12-10T23:00:25Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [January 19, 2024, 1:54pm UTC](https://revolt.metaeducation.com/forum/t/mold-and-load-parity/1429/6 "2024-01-19T13:54:38Z")

</div>

> [@rgchris](#):
>
> It occurred to me in [this post](https://revolt.metaeducation.com/forum/t/the-simple-things-matter-the-most/1428/8) that MOLD/ONLY appears to work at odds to other /ONLY options:

Historical MOLD/ONLY is indeed backwards...

...which motivated making an exception for MOLD not taking antiforms for splices. MOLD of a splice will [mold the contents with no delimiters](https://revolt.metaeducation.com/forum/t/mold-only-vs-mold-spread/2059):

```
>> mold [a b c]
== "[a b c]"

>> mold spread [a b c]
== "a b c"

```

Nice and neat.

> [@hostilefork](#):
>
> So you can put together a thought like:
> 
> ```
> >> something: "1"
> 
> >> ensure integer! single of load something
> == 1
> 
> ```
> 
> Or you could shorthand the `single of load` behavior as just **LOAD-VALUE** (I'm trying that out...)

I'm going with the concept that [DO and LOAD require a script header](https://revolt.metaeducation.com/forum/t/do-of-text-as-synonym-of-do-of-file-containing-string/2125).

Also: LOAD was previously needed to get an initial binding. But with pure virtual binding, unbound code is a more practical currency, and you should be getting an unbound value back from "LOAD-VALUE".

So that's two reasons why LOAD-VALUE is badly named in the current world. It's really TRANSCODE:ONE, plus ensuring that there's no leftover. Output lacks a binding and input lacks a header, so it's not LOAD-like.

Calling it **`transcode:one`** is accurate, though a little wordy... ☹

I don't know what the alternatives would be. TO-VALUE?

```
>> to-value "{abc}"
== {abc} ; a text! value... but "{abc}" was a text! value too

```

Maybe learnable that it really means (STRING-)TO(-TRANSCODED-SINGLE)-VALUE without having to write that all out? But it's actually TO-ELEMENT if you want to be fully accurate, since you can't get antiforms. 😵‍💫

**I think that `TRANSCODE:ONE` is probably the best idea for this, for now.** It puts the functionality in the right place, where people who use it can find more powerful versions (or people using the more powerful versions can realize there's a simpler convenience available).

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/mold-and-load-parity/1429)._
