While there are some cases where a For loop might be reasonable, it's a general mantra – one I subscribe to myself – that "if you are using a For loop in Mathematica, you are probably doing it wrong". But For and Do loops are familiar to people who already know other programming languages. It is common for new Mathematica users to rely on loop constructs, only to become frustrated with performance or code complexity.
My question is: are there some general rules of thumb that would help new users select the appropriate alternative to a procedural
FororDoloop, and are there other useful Mathematica constructs, aside fromRandomVariate/Nest/Fold/Inner/Outer/Tuplesthat they should know about in order to avoid those loops?
In particular, there are a number of ways of iterating over lists:
The
Forloop:For[i = 1, i <= 10, i++, list[[i]] = func[ list[[i]]]The
Tablefunction operating over each part of a list in turn:Table[func[ list[[i]] ], {i, Length[list]}]The
Doloop operating over each part of a list in turn:lst = {88, 42, 25, 75, 35, 97, 12}; t = 9; Do[ x = lst[[i]]; t += Mod[x, t], {i, 1, Length[lst]} ]; tMapping a function onto each element of a list:(3 - #)/(7 * #) & /@ listAnd for nested lists, there are constructs like
MapThread:f = Mod[#, #2] Floor[#3/#] &; a = {{18, 85, 22, 20, 39}, {17, 67, 76, 96, 58}, {40, 97, 56, 60, 53}}; MapThread[f, a]
New users of Mathematica will usually pick options 1 or 3 and use C-style or Matlab approaches that involve the following multistep process:
- Defining an empty list
- Setting up a loop
- Optionally define a variable (usually not localised) to equal the iterator, which is then used in subsequent calculations within the loop
- Within each loop iteration, use the local variable defined to equal the iterator to redefine each element of that list in turn according to some function
- If the list is multidimensional, nest another loop inside that.
What are some useful guides to help users coming from other languages to Mathematica to improve the conciseness and efficiency of their code by avoiding unnecessary loops?





![CholeskyDecomposition[] example](../../images/df31246156cf8232729f6f47604110d6.webp)
R = S (*list of elemetns*); Do[ R[[i]] = f[S[[i]], G[[i]]]; , {i, Length@S}];vsR = f[#[[1]], #[[2]]] & /@ Transpose[{S, G}]The second one is more concise, but G[[i]] conveys the intent better then #[[1]].
– Ajasja Jul 05 '12 at 12:54R=Thread@f[S,G]– Simon Woods Jul 05 '12 at 13:28Thread... – Ajasja Jul 05 '12 at 13:31Compile. – Jens Jul 05 '12 at 15:12MapThread[Join,{rtmp,Rest /@ Flatten[Conjugate@rtmp, {{2}, {1}}]}]. Some may read this immediately, but I need a commented-out iterative version to be able to re-read it later (this one's faster though). – acl Jul 05 '12 at 15:34