Why Sponsor Oil? | source | all docs for version 0.16.0 | all versions | oilshell.org

Warning: Work in progress! Leave feedback on Zulip or Github if you'd like this doc to be updated.

Oil Expressions vs. Python

Oil's expression language borrows heavily from Python. In fact, it literally started with Python's Grammar/Grammar file.

This doc describes some differences, which may help Python users learn Oil.

If you don't know Python, see Expression Language and A Tour of the Oil Language.

Literals for Data Types

Literals Like Python

• Integers: 123, 1_000_000, 0b1100_0010, 0o755, 0xff
• Floats: 1.023e6 (not in the first cut of Oil)
• Lists: ['pea', 'nut']

Literals Changed

• true, false, and null (like JavaScript) rather than True, False, and None (like Python). In Oil, types are spelled with capital letters.
• String literals are like shell string literals, not like Python.
  • Double Quoted: "hello $name"
  • Single quoted: r'c:\Program Files\'
  • C-style: $'line\n'.
    • Unicode literals are \u{3bc} instead of \u03bc and \U000003bc
• Dicts: use JavaScript syntax, not Python
  • Unquoted keys: {age: 42}
  • Bracketed keys: {[myvar + 1]: 'value'}
  • "Punning": {age}

Literals Added

• Character literals are integers
  • Unicode \u{03bc}
  • Backslash: \n \\ \'
  • Pound #'a'
• Shell-like list literals: :| pea nut | is equivalent to ['pea', 'nut']
• Unevaluated expressions
  • Block ^(ls | wc -l)
  • Unevaluated expression: ^[1 + a[i] + f(x)]

Literals Omitted

• TODO: Remove tuple type. We might want Go-like multiple return values.
• List comprehensions and generator expressions. QTT over pipes should address these use cases.
• Lambdas. Functions are often external and don't have lexical scope.
• Iterators.
  • Instead we have for loop that works on lists and dicts.
  • It flexibly accepts up to 3 loop variables, taking the place of Python's enumerate(), keys(), values(), and items().

Operators

Note: Oil Does Less Operator Overloading

Oil doesn't overload operators as much because it often does automatic string <-> int conversion (like Awk):

• a + b is for addition, while a ++ b is for concatenation.
• a < b does numeric comparison, not lexicographical comparison of strings.
  • (We should add cmp() for strings.)

Operators Like Python

• Arithmetic + - * / (except they convert strings to numbers)
• // integer division, % modulus, ** (except they convert strings to integers)
• Bitwise & | ~ ^ << >>
• Logical and or not
• Ternary 0 if cond else 1
• Slicing: s[i:j] evaluates to a string
• Membership in not in
• Function Call: f(x, y)
  • What about splat * and **?

Operators Changed

• Equality === !== because we also have ~==
• Comparison operators < > <= => automatically convert strings to numbers.
  • '22' < '3' is true because 22 < 3 is true.
  • '3.1' <= '3.14' is true because 3.1 <= 3.14 is true.
• String Concatenation: ++ (not +, which is always addition)
• TODO: indexing: s[i] evaluates to an integer?

Operators Added

• Eggex match s ~ /d+/
• Glob match s ~~ '*.py'
• Approximate Equality 42 ~== '42'
• Oil sigils: $ and @
• mydict->key as an alias for mydict['key']

Operators Removed

• No string formatting with %. Use ${x %.3f} instead.
• No @ for matrix multiply.
• I removed slice step syntax 1:5:2 because 0::2 conflicts with module::name. This was only necessary for Tea, not Oil.

Oil vs. JavaScript

• Oil uses == and ~== for exact and type-converting equality, while JS uses === and ==.
• mydict->key instead of mydict.key. We want to distinguish between attributes and keys (like Python does).
• Where Oil is consistent with Python
  • Oil expressions use and or not while JS uses && || !. In shell, && || ! are already used in the command language (but they're somewhat less important than in Oil).
  • Oil's ternary operator is 0 if cond else 1, while in JS it's cond ? 0 : 1.
  • Precedence rules are probably slightly different (but still C-like), and follows Python's grammar
• Same differences as Oil vs. Python
  • s ++ t for string concatenation rather than s + t
  • Shell string literals rather than JS string literals

Semantics

Oil's syntax is a mix of Python and JavaScript, but the semantics are closer to Python.

Differences vs. Python

• Iterating over a string yields code points, not one-character strings.
  • s[i] returns an integer code point ("rune").
  • TODO: maybe this should be runeAt() and byteAt()?
• Bools and integers are totally separate types. Oil is like JavaScript, where they aren't equal: true !== 1. In Python, they are equal: True == 1.
• No "accidentally quadratic"
  • No in for array/list membership. Only dict membership.
  • The ++= operator on strings doesn't exist.

TODO

• 100 MiB? This should be multiplication?