forceValue() were called after a value is copied effectively forcing only one of the copies keeping another copy not evaluated.
This resulted in its evaluation of the same lazy value more than once (the number of hits is not big though)
--
298d93fcb860116111611a8ab0662b409734227a by Alex Strelnikov <strel@google.com>:
Release ascii_benchmark.
PiperOrigin-RevId: 205275981
--
73a01469e5862eefbe5ef9d434f45b7073476272 by Abseil Team <absl-team@google.com>:
Internal cleanup
PiperOrigin-RevId: 205236717
--
53d6338bf49dab95bd0fbb5bbcd56970c6b868c2 by Abseil Team <absl-team@google.com>:
Removes InlinedVector's dependency on bitwise operators for size_type
PiperOrigin-RevId: 205236134
GitOrigin-RevId: 298d93fcb860116111611a8ab0662b409734227a
Change-Id: I754f5eea889567add2dbbdea358a533f54a912dd
I wasn't using the previous KBDs, which were modelled after Vim's answer
for Paredit KBDs.
Some of the mappings bothered me, so I needed that made more sense to
me.
Accidentally commited the version of this configuration that has this
variable set to false.
Since most of the time, this variable should be true, commiting the true
version will clean up my git status output.
Useful since the new configuration branches according to a boolean that
encodes whether or not the Ergodox is connected.
Since I'm frequently switching between programming at my desk to
programming AFK, I need a faster way to update my Slate configuration.
Ideally - some script would watch the USB port for whether or not the
Ergo was connected. Until then...
After writing this, I have a sneaking suspiscion that I'm reinventing
something like Tmuxinator. I guess this is just a poor man's Tmuxinator.
For now, however, haven't had enough time to look into Tmuxinator as a
viable alternative, so this will have to do for now.
Furthermore, moved root-level tmux files to a subdir.
Need to learn more about `evil-goto-definition` because it is possible
and even likely that there is a known, friendlier alternative way to
dispatch the goto-definition using Evil's infrastructure. Needed a
hotfix, however, so this will have to suffice for now.
After my hard drive fried, I lost important configuration settings.
Since then, I haven't been able to use `magit-gh-pulls` without it
incessantly prompting me for my GH username and password. Until I
remember how I previously configured this, I'm disabling it.
clo was difficult to use because `company-mode` suggested autocompletion
candidates like "close", "clone", etc. With clg, this is significantly
less likely.
