Timeline for Why isn't Orderless an Attribute of And?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 23, 2016 at 7:35 | vote | accept | Soldalma | ||
| Oct 23, 2016 at 7:35 | vote | accept | Soldalma | ||
| Oct 23, 2016 at 7:35 | |||||
| Oct 23, 2016 at 5:48 | history | edited | JungHwan Min | CC BY-SA 3.0 | deleted 123 characters in body |
| Oct 23, 2016 at 3:32 | comment | added | JungHwan Min | @Szabolcs Hm, forgot about that. Thanks for telling me. | |
| Oct 23, 2016 at 3:28 | history | edited | JungHwan Min | CC BY-SA 3.0 | added 49 characters in body |
| Oct 23, 2016 at 3:27 | comment | added | Szabolcs | This property is called short circuiting and it's not only about efficiency. You can safely use a && b even when b wouldn't correctly run unless a has evaluated to True. E.g. StringQ[s] && StringStartsQ[s, "x"] | |
| Oct 23, 2016 at 3:25 | history | edited | JungHwan Min | CC BY-SA 3.0 | added 49 characters in body |
| Oct 23, 2016 at 3:18 | history | answered | JungHwan Min | CC BY-SA 3.0 |