« first day (214 days earlier)      last day (743 days later) » 

00:12
@ASCII-only yeah I did
 
2 hours later…
01:51
btw we should make wordmark
wait logo is wordmark
02:18
@ASCII-only btw I forgot to post bork but there is big bork:
vsl:parser> (1 + 1) + 1

readline.js:973
            throw err;
            ^
ono ambiguity ;_;
btw can you add as, as?, and as! as binary op
@Downgoat pls no
ono ;_; y u sai dis
@Downgoat because baaaaaaaad
ono i am turning into eivl shep
;_; how
@ASCII-only ;________; ono 0/10 evil sheep pls stahp posses asci-only
@Downgoat no
02:23
@Downgoat pls try now
vsl:parser> (1 + 1) + 1

readline.js:973
            throw err;
            ^
ono ambiguity ;_;
did you rebuild
@Downgoat y u kick i thought shep is gaots cousin
ono shep is eivl
0/10 very offsneive
shit mispell
:D fixed
@ASCII-only why no as? as stuffs?
@Downgoat as should be ::
as? should be as
hmmmmmm
we still need 3 casts
1) that return optional 2) that is forced and will throw error if fail 3) that can be compile-time (e.g. int -> int64)
02:28
1) as 2) :: 3) ::
using both :: will violate type saftey though
?????????????????????????????????????????????
@ASCII-only pls wat confuse
we should not check Int -> Int64 cast at runtime
if I do Array::"goat", this should fail at compile-time
because neither lay on same branch in type hierarchy
@Downgoat yeah i know
@Downgoat yeah
so we should have seperate cast for that no?
maybe just as?, as, and ::
idk that isn't perfect though
we need at least as for sure though right?
so we should add that
@ASCII-only wait var a = a? should be valid
currently don't work
bork alert:
vsl:parser> var x = (a?.b)?.c
token { value: '.' }
readline.js:973
            throw err;
            ^

Error: [object Object]
Unexpected "."

    at Parser.feed (/home/ubuntu/workspace/node_modules/vsl-nearley/lib/nearley.js:317:23)
02:40
@Downgoat is (1+1) +1 still bork
@ASCII-only that work now :D
@Downgoat oh yeah didn't do ?. operator yet
oh
I think we should just do ?
because of var a = b?
@Downgoat um what
like as suffix
02:41
????????????????????????????????????????????????????????????????????????????????‌​??????????????????????
ono is quesitonmark key stuck? :P >_<
1 min ago, by Downgoat
because of var a = b?
that is valid
so can't be ?. has to be ?
we might also need to add more property expression nodes. e.g.: a.b is PropertyExpression { a, b } or a.b.c becoming: PropertyExpression { a, PropertyExpression { b, c } }
that way PropertyExpression can have optional attribute
@Downgoat like a?b?c?
see example
I think part of article got lost in copy+ paste fail
. can be operator though
I mean it doesn't really make sense imo to have BinaryExpression { op: ".", lhs: a, rhs; b }
for a.b
02:50
how
well I mean for starters a and b are not expressions
how are they not
will also make thing like 1.1 ambiguous
@ASCII-only You can't do a.(1 + 1)
@Downgoat no it won't because 1.1 is a single literal
still
1.[1,2,3] also shouldn't be thing
02:51
@Downgoat hmmm ok
03:22
@Downgoat ok what do i do now
03:52
i have to study for final tomorrow but if you can work on scope generation that would be very very helpful
i have the stuff pretty well documented
 
20 hours later…
23:45
@ASCII-only wait how to do interface
are we need to pass function pointer?
@ASCII-only btw in as it should allow any type
also generics should be allow in normal property expression, e.g.: let thing = A<B>.C<D>()

« first day (214 days earlier)      last day (743 days later) »