These are chat archives for Gozala/wisp

26th
Feb 2015
Irakli Gozalishvili
@Gozala
Feb 26 2015 17:44
@rcarmo that would be great, please do!
@rcarmo I’d be also ok with ditching node@0.8 I think
Adam Avramov
@egasimus
Feb 26 2015 19:02
@gozala Hey, this Gitter thing is pretty cool :)
Adam Avramov
@egasimus
Feb 26 2015 19:17
anyway, yeah, my situation is a bit more complicated than could fit in 160ish characters
Irakli Gozalishvili
@Gozala
Feb 26 2015 19:17
@eivindj sorry I’m at the meeting right, now I’ll ping you once I’m out
Rui Carmo
@rcarmo
Feb 26 2015 19:39
Hey @Gozala! :) I'm kind in the middle of a few things now, but will try updating deps when I need to do something relaxing (yeah, I know... by the way, get much sleep lately?)
Irakli Gozalishvili
@Gozala
Feb 26 2015 19:41
@rcarmo yeah it’s not that bad actially, my time constraints are actually more related to the the day job :)
@egasimus ok so I’m aronud
@egasimus and yeah macro imports is the absolutely a think that has being p1 for me for quite some time. I had a work in progress patch to get there but it’s not done yet I’m afraid.
@egasimus that being said some ppl suggested to point a compiler to files with macro definitions to incorporate those during compilation
@egasimus implementing that should be quite easy I think
@egasimus what some ppl do I think is create custom scripts that import compiler + macros they want and in that case macros will be available for the scripts it’s going to be compiling
@egasimus to implement proper macro import, some changes to the anaylzer and compiler are required.
Irakli Gozalishvili
@Gozala
Feb 26 2015 19:47
  1. Namespaces support right now is kind of really weak, so that needs to be fixed & I have some patch laying around that I think does that, but was breaking a test that I did not had time to digg into.
  1. Once namespaces are there, analyzer will need to handle imports (currently it does not do that), by which I mean it needs to actually read imported modules and register encountered macros.
  1. Once thos two pieces are in place macro expander code will just need to take macro namespaces into account.
@egasimus if you’ll have intereset on hacking on any of these I’d be happy to help as I can.
Irakli Gozalishvili
@Gozala
Feb 26 2015 19:53
In terms of when I’ll be able to do it myself, I’m afraid I don’t have an answer, but as things look right now I don’t imagine soon.
Adam Avramov
@egasimus
Feb 26 2015 20:59
@Gozala thanks for the detailed description (and sorry for my own intermittent absence). I'm definitely interested in having a go at this and learning about how the Wisp compiler works. What do you have in mind regarding namespaces? Something closure-based? Actually if that patch is somewhere in the repo I can give it a whirl :)
Irakli Gozalishvili
@Gozala
Feb 26 2015 21:05
@egasimus I meant namespaces in a way namespaces are used in clojure, in compiled JS they won’t even be there
@egasimus let me see where that patch is
Irakli Gozalishvili
@Gozala
Feb 26 2015 21:21
@egasimus sorry I got distracted
so here are some branches I’ve being working on
@egasimus can’t really recall why I was doing it though
Irakli Gozalishvili
@Gozala
Feb 26 2015 21:27
@egasimus can’t find the analyzer work I’ve benig doing
@egasimus it could be that I have landed it already
Irakli Gozalishvili
@Gozala
Feb 26 2015 21:32
@egasimus ok so I had discussed implemenatation strategy with other person before who had interest working on it & there are pointers to patches I have / had. I think it would be best for you to read through and followup on that thread if you’de be interested to pick it up from there
Gozala/wisp#3
@egasimus At this point I think it won’t be unreasonable to start with what has being suggested here as well