diff options
| author | EuAndreh <eu@euandre.org> | 2021-04-24 17:50:22 -0300 |
|---|---|---|
| committer | EuAndreh <eu@euandre.org> | 2021-04-24 17:50:44 -0300 |
| commit | b7bc24827c15e802c867eefdc562fab0db1b49af (patch) | |
| tree | d5259134fd3bd9af234df0b331e7fb1a9415b117 /locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po | |
| parent | Add po files for new TILs, update whitespace of others (diff) | |
| download | euandre.org-b7bc24827c15e802c867eefdc562fab0db1b49af.tar.gz euandre.org-b7bc24827c15e802c867eefdc562fab0db1b49af.tar.xz | |
Proofread TIL on CLOS
Diffstat (limited to 'locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po')
| -rw-r--r-- | locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po | 39 |
1 files changed, 26 insertions, 13 deletions
diff --git a/locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po b/locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po index b773879..4ca9625 100644 --- a/locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po +++ b/locale/pt/LC_MESSAGES/_tils/2021-04-24-common-lisp-argument-precedence-order-parameterization-of-a-generic-function.po @@ -121,12 +121,6 @@ msgid "" msgstr "" msgid "" -"CLOS has to make a choice between the first and the second definition of " -"`yet-another-fn`, but its choice is just a heuristic. What if we want to the" -" choice to be based on the second argument first?" -msgstr "" - -msgid "" "For that, we use the `:argument-precedence-order` option when declaring a " "generic function:" msgstr "" @@ -169,13 +163,6 @@ msgid "" msgstr "" msgid "" -"When declaring a class, we can choose the precedence order, and that is " -"about it. But when defining a generic function, the order of argumentws is " -"more important to the function semantics, and the argument precedence being " -"left-to-right is just the default behaviour." -msgstr "" - -msgid "" "One shouldn't change the order of arguments of a generic function for the " "sake of tailoring it to the CLOS priority ranking algorithm, but doing it " "for a class definition is just fine." @@ -183,3 +170,29 @@ msgstr "" msgid "TIL." msgstr "" + +msgid "" +"CLOS has to make a choice between the first and the second definition of " +"`yet-another-fn`, but its choice is just a heuristic. What if we want the " +"choice to be based on the second argument, instead of the first?" +msgstr "" + +msgid "" +"When declaring a class, we can choose the precedence order, and that is " +"about it. But when defining a generic function, the order of arguments is " +"more important to the function semantics, and the argument precedence being " +"left-to-right is just the default behaviour." +msgstr "" + +#~ msgid "" +#~ "CLOS has to make a choice between the first and the second definition of " +#~ "`yet-another-fn`, but its choice is just a heuristic. What if we want to the" +#~ " choice to be based on the second argument first?" +#~ msgstr "" + +#~ msgid "" +#~ "When declaring a class, we can choose the precedence order, and that is " +#~ "about it. But when defining a generic function, the order of argumentws is " +#~ "more important to the function semantics, and the argument precedence being " +#~ "left-to-right is just the default behaviour." +#~ msgstr "" |