diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2021-06-11 19:33:08 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2021-06-11 19:33:08 -0700 |
| commit | ef29fcdc9170dec59c1b38f01e72cb8ad8c69550 (patch) | |
| tree | ad888d1034765aa9697148a44ff0a6a45a280886 /linux/assort | |
| parent | cbf3de0f0814bbca23a9702574425742895bc834 (diff) | |
| download | mu-ef29fcdc9170dec59c1b38f01e72cb8ad8c69550.tar.gz | |
cancel pending test
After all that, I'm not sure this is the desired behavior. If a function defines multiple bindings, we shouldn't rename all their keys. So how to choose? Perhaps it's not so bad to have "symlinks" in this "file system". To unlink two bindings you now need to define one of them in the sandbox. All the refactoring is still useful, though.
Diffstat (limited to 'linux/assort')
0 files changed, 0 insertions, 0 deletions