You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -166,9 +166,9 @@ func greet { person =>
166
166
167
167
in Lithia are different than you might know them from other languages.
168
168
Other languages define enums as a list of constant values. A few allow associated values for each named case.
169
-
A Lithia *enum* is an enumeration of types.
169
+
A Lithia _enum_ is an enumeration of types.
170
170
171
-
There is syntactic sugar for value enumerations, to directly declare a case and the associated *enum* or *data* type.
171
+
There is syntactic sugar for value enumerations, to directly declare a case and the associated _enum_ or _data_ type.
172
172
173
173
```
174
174
enum JuristicPerson {
@@ -407,7 +407,7 @@ Most languages allow type casts and checks. Lithia does only support the type sw
407
407
408
408
These checks are unstructured and therefore tempt to be used in the wrong places. Though type checks should be used sparingly. Lithia prefers to move required decisions to the edge of the code. Witnesses should implement decisions for the provided data and desired behavior.
409
409
410
-
If there is one type to focus on, the tooling and the developer can understand all cases much easier and faster.
410
+
If there is one type to focus on, the developer and the tooling can understand all cases much easier and faster.
0 commit comments