In programming languages, literals are textual representations of values in the source code. This is a syntactical concept.
Some examples:
7 # integer literal
<details><summary>Zed.log</summary><pre> | |
<!-- Click below this line and paste or drag-and-drop your log--> | |
2024-10-04T00:04:02.983854-04:00 [INFO] ========== starting zed ========== | |
2024-10-04T00:04:02.988191-04:00 [INFO] Opening main db | |
2024-10-04T00:04:02.990823-04:00 [INFO] Opening main db | |
2024-10-04T00:04:03.018765-04:00 [INFO] Using git binary path: Some("/Applications/Zed.app/Contents/MacOS/git") | |
2024-10-04T00:04:03.229928-04:00 [ERROR] invalid binding value for keystroke cmd-alt-enter, context Some("Editor") | |
Caused by: | |
no action type registered for editor::NewLineAbove |
## you presumably already know that this returns false, because of the way floats are stored: | |
0.1 + 0.2 == 0.3 | |
# => false | |
# we can create a more useful way of comparing floats that matches what humans would expect: | |
class Float | |
def =~(number, tolerance = 0.0001) | |
(self - number).abs < tolerance | |
end |
In programming languages, literals are textual representations of values in the source code. This is a syntactical concept.
Some examples:
7 # integer literal
Overview | |
-------- | |
Consider the commands given to be examples, not to necessarily be precisely | |
what you will use. They were based on my circumstances, in which | |
* my local platform is macOS, | |
* where Homebrew is the de facto package manager; | |
* my laptop (and the server) are managing Ruby with rbenv; | |
* vim is my remote editor of choice, and an acceptable local editor; and |
Goals | |
Editable by Supervisor | |
Employee Data Safe | |
Supervisor Edits Goals -> Editable by Supervisor | |
Supervisor Assigns Rights to Employee -> Editable by Employee | |
Employee Data Lost | |
No Simple Solution -> Employee Data Lost | |
Editable by Employee | |
Employee Data Still Safe | |
Employee Begins Editing Goals -> Employee Data at Risk |
# https://wikihub.berkeley.edu/display/robots/CC+-+20181213+More+Changes+to+Pilot+Specs | |
Proposed Performance Pilot Workflow - Newest | |
No Review Exists* | |
Create New Form -> Supervisor Starts Form | |
Review In Process | |
Supervisor Starts Form | |
Save -> Draft | |
Save & Share with Employee -> Participants Comment and Sign | |
New* | |
Draft |
Proposed Performance Pilot Workflow - Steps | |
No Review Exists* | |
Create New Form -> Supervisor Starts Conversation | |
Review In Process | |
Supervisor Starts Conversation | |
Save as Draft -> Supervisor Starts Conversation | |
Share with Employee -> Participants Comment | |
Participants Comment | |
Employee Comments -> Participants Comment | |
Supervisor Edits and Comments -> Participants Comment |
Proposed Performance Pilot Workflow - States | |
No Review Exists* | |
Create New Form -> New | |
Review In Process | |
Save as Draft -> Draft | |
Share with Employee -> Awaiting Comments | |
Delete -> No Review Exists | |
New | |
Draft | |
Awaiting Comments |
Proposed Performance Pilot Workflow - Complete | |
No Review Exists* | |
Create New Form -> Supervisor Starts Conversation | |
Review In Process | |
Supervisor Starts Conversation | |
Save as Draft -> Draft | |
Share with Employee -> Participants Comment | |
New* | |
Draft | |
Participants Comment |