Timeline for How does MapThread work with Associations?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 16, 2014 at 9:18 | history | edited | kglr | CC BY-SA 3.0 |
added 16 characters in body
|
| Oct 16, 2014 at 9:10 | comment | added | kglr | Mr.W it is indeed... | |
| Oct 16, 2014 at 9:09 | comment | added | Mr.Wizard |
One down, one to go. (grin) Now realize that MapThread[(# + #2) &, {x, y}, 0] is merely x + y.
|
|
| Oct 16, 2014 at 9:07 | comment | added | kglr | @Mr.W got it ... finally ... thanks:) | |
| Oct 16, 2014 at 9:04 | history | edited | kglr | CC BY-SA 3.0 |
deleted 3 characters in body
|
| Oct 16, 2014 at 8:55 | comment | added | Mr.Wizard |
In your example using Thread, Thread is superfluous; you are merely adding the two associations which triggers automatic threading. Likewise the use of MapThread with levelspec 0. See eldo's deleted answer and my just-posed question on the subject.
|
|
| Oct 16, 2014 at 8:46 | history | edited | kglr | CC BY-SA 3.0 |
added 72 characters in body
|
| Oct 16, 2014 at 8:45 | comment | added | Mr.Wizard |
+1 but realize that only Map is important here; e.g. Evaluate is incidental.
|
|
| Oct 16, 2014 at 8:41 | history | answered | kglr | CC BY-SA 3.0 |