Maybe it could be useful to define what should be included in the vlib and what should be included in extra lib.
My proposition is to have a quite small vlib, focused on essential features and heavily tested. And some other directories which include cool stuff but maybe less useful for everyone.
yep84
All 4 comments
Would be great, if V and Vlib is targeting embedded devices (small code size, no dynamic features) and can be extended for general purpose on other machines (eg. dynamic memory, gc, etc... )
alfclement
on 9 Jul 2019
It's going to be very similar to Go's standard library.
medvednikov
on 10 Jul 2019
I agree, I think vlib should be only has core libs. Which written in pure V.
The extra ones like libs which use some or depends of/on c libs like open GL or any gui libs must be in other place.
hamad-almamari
on 18 Jul 2019
gg, ui, glfw, gl, pg etc are not part of vlib and will be moved this week, once user modules are supported.
medvednikov
on 18 Jul 2019
Related issues
medvednikov
路
3Comments
markgraydev
路
3Comments
jtkirkpatrick
路
3Comments
vtereshkov
路
3Comments
lobotony
路
3Comments
Most helpful comment
gg, ui, glfw, gl, pg etc are not part of vlib and will be moved this week, once user modules are supported.