Right, I assume so that we can pass in other Iterable objects than a literal list. 

I would definitely support that but I'd like to get this PR in before it becomes long lived. As long as the most simple case is tested and works we can improve upon it for next release. 

Sent from my mobile

> On Nov 30, 2013, at 12:32 AM, Abhishek L <notifications@github.com> wrote:
> 
> In hy/contrib/anaphoric.hy:
> 
> > +;; all copies or substantial portions of the Software.
> > +;;
> > +;; THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> > +;; IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> > +;; FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
> > +;; THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> > +;; LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> > +;; FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> > +;; DEALINGS IN THE SOFTWARE.
> > +;;
> > +;;; These macros make writing functional programs more concise
> > +
> > +
> > +(defmacro ap-each [lst &rest body]
> > +  "Evaluate the body form for each element in the list."
> > +  `(foreach [it ~list] ~@body))
> lst is passed as the argument and must be evaled
> 
> —
> Reply to this email directly or view it on GitHub.