@dom96
Is there a list of tasks that need to be completed before 1.0? I'm not very
experienced when it comes to working on a programming language, but I'm willing
to learn. I could start with small bugfixes and the like.
> Cool, thanks for sharing. I like the KISS approach.
Admittedly, the KISS approach is probably a product of my inexperience with Nim
rather than any sort of design decision.
> I'd like to see dynamic routes, redirects and static file handling along the
> lines of python's bottle:
Dynamic
Cool, thanks for sharing. I like the KISS approach.
> Does anyone have anything specific they would like to see in a url routing
> library?
I'd like to see dynamic routes, redirects and static file handling along the
lines of python's bottle:
No to temper you enthusiasm, but I think this is a serious issue
[https://github.com/dom96/choosenim/issues/13](https://github.com/dom96/choosenim/issues/13)
I think choosenim should be the official way to install Nim recommended on the
site. I love it already, it's so damn convenient compared to using native
package managers!
The only mild inconvenience I can see right now is that choosenim can't update
itself. And maybe the lack of docs.
The issue with `foo2` and `foo3` is one and the same: when called from a
generic proc, untyped-arguments templates in them won't be used for type
annotations. Your `getType` is not used then, so `macros`'s one used, if you
import it, what you can see by using explicit `your_module_name.getType`
> an std::shared_ptr ... then `ref A` takes over the ownership
Is it the same when the backend is C?
Have compiler already warned if there's untracked reference cast to tracked
reference?
> It would be cool if nimble install X just installed stuff in the current
> folder's 'lib/pkgs/deps' directory and updated/created .nimble to reflect the
> installed dependancies and their versions
It would be much better if nimble could recognize two different dependency lib
that depend on
@Araq,
Fiddled around in the generated C file in the **nimcache** directory by adding
code to load the library **libpython3.5m.so.1.0** in C directly and it throws
the same error!
The added code (added to the generated **PyInit_nim_module** function) is:
N_CDECL(...,
