Thanks for the reply. It has been awhile since I read the tutorial.
However, when searching [https://nim-lang.org/docs/lib.html](https://nim-lang.org/docs/lib.html) I do not find the int() procedure. I do not find any procedure answers the question of how to provide the right type. Yes I understood the error message. It was readily apparent. It was getting from where I am to where I want to be that I could not find a path. My question is and has been is there something I am missing from the standard documentation or is the standard documentation at present not at a place to provide answers like this. I still do not see where this is defined. And this is for a question we know the answer to. Let alone a question that I do not know the answer and have not asked. Nim has different challenges with regard to discoverability. In your OO languages you generally find all methods associated with a Type in the class definition. As they generally lack the ability to modify the class and add methods anywhere else. Smalltalk is a little different in this regard. Regarding Smalltalk and Python. I am a long time user of both. Python longer, but Smalltalk more. I enjoy Pharo. I am able to do my app in Pharo and may do so. I have this app partially in Nim, Python and Pharo. Most recent exploration in Python showed significant performance problems. So I wanted to explore Nim some more. Nim is very different from Pharo or Python. There is much I like about Nim. The things I don't like are not necessarily problems with Nim, but rather my lack of experience with Statically typed and statically compiled languages. That is something that I do want to learn over time. I love the idea of small, fast, memory efficient apps. I hate the current trend towards lazy, bloated and slow apps. I have explored many, many languages over the course of many years. I am not a professional programmer. I have a day job and a family. So like many people, time is limited. Nim looks like it hits a pretty sweet spot with its syntax, performance, etc. It's current or past state of maturity has been its most limiting factor for me. I have limitations in skill, and time to acquire said skill. However, Nim is getting close to the place where my skills and its maturity are able to start doing things. I am one of the people you refer to. Looking at my profile, I have been registered for a little over 3 years with 24 posts. Most of my reasons of stopping my attempt with Nim has been the combination of where I was skillwise and where Nim was maturity wise. But I have come and gone a number of times. I keep checking back. I think there are probably a lot of people like me. And as Nim matures and its ecosystem grows. The ability for people like me to use Nim will improve. I have also explored Rust, Kotlin, OCaml, C++, C. I really like Nim. I think Andreas has created a beautiful language. I think he made a lot of great decisions. And now that there is a little money behind Nim. I think the future is bright. Nim is different from what I am used to. But different is not bad, it is simply different. I take full responsibility for the problems being with me and not Nim. I am not assigning any blame Thanks for the suggestion of the IRC. I had forgotten about that. I am used to mailing lists. I will check out the IRC channel and try there first unless it is something more permanent which deserves post on the forum. Again, thanks for engaging in conversation. This is a good community. :)
