|
|
|
|
|
by Firadeoclus
858 days ago
|
|
This is a really interesting system, and I'm excited to give this a try! Without knowing whether the following cases would actually be useful/relevant, I'm curious if these things apply to Unison: - Is there a way to "pin" a symbol to a specific hash/version so it won't automatically update when the referred function gets a change? I.e. I could write:
A = B@ ++ "world"
and when I store and retrieve it, it becomes (example syntax):
A = B@a3yx ++ "world" - Is there a way to refer to a function/symbol by name rather than by hash? I.e. a call site which uses B by looking up which hash is currently associated with the name "B", such that if I do two simultaneous renames, B->D and C->B, the code would now refer to the function previously known as C? - Are there ways in which the way function updates "bubble up" through the codebase (I assume updating a function means updating every function that calls it, recursively) could become a problem? It would seem that changing one little function could have a knock-on effect that requires re-hashing most of the codebase. |
|