Skip to content

Fix typo "priori" -> "prior" #8573

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
domesticmouse merged 4 commits into from
Apr 25, 2023
Merged

Fix typo "priori" -> "prior" #8573

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6cdf0da
Fix typo "priori" -> "prior"
Apr 18, 2023
3ee43e8
Merge branch 'main' into main
domesticmouse Apr 19, 2023
e94c2db
Update src/resources/inside-flutter.md
sfshaza2 Apr 25, 2023
193d074
Merge branch 'main' into main
sfshaza2 Apr 25, 2023
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
2 changes: 1 addition & 1 deletion src/resources/inside-flutter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -586,7 +586,7 @@ Some interpolatable objects are defined by class hierarchies. For example,
shapes are represented by the `ShapeBorder` interface, and there exists a
variety of shapes, including `BeveledRectangleBorder`, `BoxBorder`,
`CircleBorder`, `RoundedRectangleBorder`, and `StadiumBorder`. A single
`lerp` function cannot have a priori knowledge of all the possible types,
`lerp` function can't anticipate all possible types,
and therefore the interface instead defines `lerpFrom` and `lerpTo` methods,
which the static `lerp` method defers to. When told to interpolate from
a shape A to a shape B, first B is asked if it can `lerpFrom` A, then,
Expand Down