VSL

ASCII-only

12:43 AM

@Downgoat ok so

idk about as?, as! and try?

ok first

what is difference between as? and as!

Downgoat

as! is OO-cast and will throw error if cast fail

as? is OO-cast and will return nil if fail

ASCII-only

@Downgoat that's what normal as should do

Downgoat

normal as will ensure cast will never fail

i.e. throw compile-time error is possibility of fail

ASCII-only

ok wat

Downgoat

e.g. downcast may fail

but upcast can be done with as as upcast can never fail

like if I do let someAnimal = Dog as Animal and then do someAnimal as Goat, that will fail

ASCII-only

12:48 AM

@Downgoat isn't normal as just neverfail::MyType

Downgoat

that is for non-OO cast

ASCII-only

what why different cast 0/10

Downgoat

because do different things

:: can comile to list a zest or a sext instruction

as needs much more complex type alignment stuffs

we should get SO tag going for VSL when start to work

Downgoat

1:25 AM

@ASCII-only btw things that need to be parsed: github.com/vsl-lang/VSL/…

ASCII-only

2:04 AM

@Downgoat :(

Downgoat

@ASCII-only D: y y haet zests and sexts ;_;

shit came out wrong

ASCII-only

@Downgoat haha

@Downgoat no i mean why can't you just special case non oo cast

Downgoat

Too complex

And slow

ASCII-only

0/10 how

Downgoat

Because then have to manually determine inheritance and all

ASCII-only

2:12 AM

@Downgoat ???

Downgoat

@ASCII-only like we'd then need a more complex verification stage

idk if you don't want two we don't need to have two

but as is kinda long:

e.g.:

pow(base: base as Double, power: power as Double)

compared to:

pow(base: Double::base, power: Double::power)

ASCII-only

@Downgoat yeah i meant use :: instead of as

@Downgoat O_o you can use casts in function arglists?

Downgoat

why not?

ASCII-only

2:37 AM

@Downgoat what does that even do

Downgoat

convert base and power variable to double

example: github.com/vsl-lang/VSL/blob/master/src/libraries/libvsl/…

ASCII-only

@Downgoat ok wat where does t come from

Downgoat

oh shit

oops

@ASCII-only hm, should we use KVC

developer.apple.com/library/content/documentation/General/…

Downgoat

11:18 PM

@ASCII-only halp array bork. Im do var a: goat[]

also dictionary bork:

TypeError: t.DictionaryNode is not a constructor

same with SetNode

same with array

ASCII-only

@Downgoat ok fix

Downgoat

thanks

btw what is syntax for immmutable dictionary

;_; typealias does bork

ASCII-only

@Downgoat like tuple: (foo: 1, [1 + 1]: 2)

Downgoat

ono

problem: that is named tuple syntax ;_;

ASCII-only

@Downgoat wait what

Downgoat

11:26 PM

like tuple but each element has name

ASCII-only

@Downgoat because you forgot to add to tokenizer?

@Downgoat 0/10 bad idea

Downgoat

D:

ASCII-only

that is what struct is for

Downgoat

tuple also faster than struct

ASCII-only

@Downgoat how

Downgoat

11:29 PM

because struct uses myStruct.init.n methods

also sometime struct not always most idomatic

like converting from array -> tuple is much more nice than array -> struct

ASCII-only

@Downgoat but how do you convert from array to named ttuple

Downgoat

named tuple's named don't have any semantic significance

they are just to make cleaer than [0]

like what is more clear:

(String, UInt)

or:

(username: String, id: UInt)

quartata

@Downgoat Unless we're operating under different definitions of struct that's not possible

What you just described is a struct

Downgoat

4 mins ago, by Downgoat

because struct uses myStruct.init.n methods

so yes different defnition of struct

has different internal behavior and all

quartata

maybe your structs shouldn't do that

in C++ if a class is POD it doesn't do that

Downgoat

11:34 PM

also may have different GC behavior

quartata

450

A: What are POD types in C++?

POD stands for Plain Old Data - that is, a class (whether defined with the keyword struct or the keyword class) without constructors, destructors and virtual members functions. Wikipedia's article on POD goes into a bit more detail and defines it as: A Plain Old Data Structure in C++ is an ag...

Downgoat

@quartata plastic orange disorder?

quartata

preempted that

Downgoat

@quartata structs are like classes in VSL

they are not like C types

while they may be represented like them

quartata

read the link I just posted

Downgoat

11:35 PM

they still have initalizers and all that good stuff

@quartata ok

quartata

If a class follows those criteria C++ compilers just turn it into a "normal" struct

Downgoat

cool

quartata

since it's just plain old data with no constructor funny business

I'd say using structs like that is much easier for typing

A named tuple would be basically anonymous: (foo: Integer, baz: String)

Downgoat

tuples are immutable however

in context of LLVM that is big difference

also for GC

makes tracking lifetimes much simplier

quartata

Are you doing Rust memory management

Downgoat

11:39 PM

wat

ASCII-only

@Downgoat so are structs?

struct = basically immutable class

quartata

@ASCII-only what?

Downgoat

yeah, in the terms that it won't be reallocate but pointer can be change

that mean new object to attach to lifetime of struct

ASCII-only

@quartata wait it isn't?

quartata

@ASCII-only Not in C++

Downgoat

11:43 PM

Btw we will need to write doc generator for VSL

ASCII-only

@quartata well I meant in VSL it will probably be just an immutable class

@Downgoat imo we should have some kind of builtin doc support in the language

Downgoat

@ASCII-only yeah definetly

I've added java-doc style comments to existing VSL STDLIB

btw minor bork:

          Array {
            parentScope: null,
            parentNode: null,
            array:
             [ [ ExpressionStatement {
                   parentScope: null,
                   parentNode: null,
                   expression: Literal { parentScope: null, parentNode: null, literal: '1', type: 0 } } ],
               [ ExpressionStatement {
                   parentScope: null,
                   parentNode: null,
                   expression: Literal { parentScope: null, parentNode: null, literal: '2', type: 0 } } ] ],

Expression statements should not be wrapped in array

might need {% id %} somewhere or something

@ASCII-only btw super duper important: do not forget to implement get children

ASCII-only

@Downgoat pls no comment docs

Downgoat

wat

quartata

@ASCII-only ?

Downgoat

11:45 PM

are you suggesting semantics for docs?

github.com/vsl-lang/VSL/blob/master/src/libraries/libvsl/…

doesn't look bad or anything

quartata

@inline @unsafe looks kind of weird

Downgoat

pls suggest alternative syntax

quartata

@inline
@unsafe

Downgoat

Question: should I mark libc function like memcpy as unsafe

quartata

would be what I'd expect

Downgoat

11:48 PM

you can do serious bork with them

quartata

unsafe usually means pointer arithmetic

so yes?

I think?

Depends on your implementation

Downgoat

I am doing direct link from libc:

github.com/vsl-lang/VSL/blob/master/src/libraries/libc/libc.vsl

quartata

*of libc

Downgoat

someone needs to typo check my docs

quartata

Oh no that's me correcting myself

"Depends on your implementation of libc"

nothing to do with you

Downgoat

11:51 PM

oh

glibc

quartata

although if I accidentally discovered a typo in your docs that would be amusing

Downgoat

btw do you happen to know what FILE* in C actually is?

I have typealias FILE = OpaquePointer atm >_>

quartata

OS dependent

So just treat it like void *

Downgoat

shit i dont think llvm allow named opaque type

@ASCII-only btw what is type heirarchy for number

I say the hackmd

quartata

Just wrap it in something?

Downgoat

11:54 PM

but we need a SignedInt vs UnsignedInt class

quartata

I mean I hope you're going to have a wrapper around filehandles anyways

Because C file I/O is unfun

Downgoat

oh

well libc is literally libc binding

in libvsl we will have nice fs class or something

quartata

then don't bother giving it a name for now

it's just a number that's the size of your architecture's pointers

Downgoat

actually looks like LLVM just makes i8* a void*

wait actually I can just do @FILE = type opaque :D

Quesiton: does reflection infos go in .DATA section

ASCII-only

@Downgoat yeah

Downgoat

11:56 PM

@ASCII-only sorry I mean to say I saw

2 mins ago, by Downgoat

but we need a SignedInt vs UnsignedInt class

they are seperate instruction for signed div vs unsigned div

also will allow for special optimization]

ASCII-only

yes

SignedInt = normal Int so imo you don't need it

Downgoat

ok

then we need unsignedint class

because we will have like UInt64 snd UInt8

and regular UInt of course

btw do we want typealias Size = UInt or something like that?

shit I think it is actually UInt64

Transcript for