Timeline for Thread a function over a list and with a non-atomic 2nd parameter?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2013 at 19:56 | comment | added | Leonid Shifrin | @alancalvitti Thanks for the accept. It's been a while :-). | |
| Feb 19, 2013 at 19:42 | vote | accept | alancalvitti | ||
| Aug 25, 2012 at 22:35 | comment | added | Leonid Shifrin |
@alancalvitti The probem is that Listable is an attribute, not a function. As such, it is wired quite deeply into the evaluation sequence. And evaluator does not have any tuning parameters, it is not even clear how you can define such parameters locally (so that they will apply to a specific head in a given place of code).
|
|
| Aug 25, 2012 at 22:29 | comment | added | alancalvitti | Thank you Leonid - so far this looks like the best hope, I will likely accept shortly (still looking through your web site) though I was hoping to avoid custom functions. Could WRI have implemented a Level option functionality for Listable to achieve this? | |
| Aug 25, 2012 at 22:12 | history | answered | Leonid Shifrin | CC BY-SA 3.0 |