Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Change confusing use of pure
Remove the possibly confusing use of pure
  • Loading branch information
yunti authored Aug 19, 2020
commit 5a78d418c2bdce99edb2016a75f4935fd41ed128
2 changes: 1 addition & 1 deletion pages/docs/manual/latest/introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ We respect TypeScript very much and think that it's a positive force in the Java

- Consequently, TypeScript's type system is necessarily complex, pitfalls-ridden, potentially requires tweaking, sometime slow, and requires quite a bit of noisy annotations that often feel like manual bookkeeping rather than clear documentation. In contrast, ReScript's type system:
- Is deliberately curated to be a simple subset most folks will have an easier time to use.
- Has **no** pitfalls, aka the type system is "sound" (the types will always be correct). E.g. If your value is not null, it'll never lie and slip through some `undefined` value. **Pure ReScript programs have no null errors**.
- Has **no** pitfalls, aka the type system is "sound" (the types will always be correct). E.g. If your value is not null, it'll never lie and slip through some `undefined` value. **Programs with just ReScript code have no null errors**.
- Is the same for everyone. No knobs, no bikeshedding opportunity.
- Runs extremely fast precisely thanks to its simplicity and curation. We're one of the fastest compiler & build system for JavaScript development.
- **Doesn't need type annotations**. Annotate as much or as little as you'd like. The types are inferred by the language (and, again, are guaranteed correct).
Expand Down