> Can you point to some examples of this in the Rust community?
[https://github.com/rust-lang/rust/pull/25640](https://github.com/rust-lang/rust/pull/25640)
[https://github.com/rust-lang/rust/issues/25650](https://github.com/rust-lang/rust/issues/25650)
@Araq Sorry if I'm a bit slow on the uptake, but I'm not sure about what you
meant. libuv is wrapped in the stdlib, which is great, but if it's really based
on a 3+ yo version (is it?), AND libuv is updated regularly, which it is, then
I do see the need for a non-stdlib that is more recent. If
This is probably not applicable to what you are trying to do, but maybe you
want to use a reference instead?
type Person = ref object
first, last: string
let person1 = Person(first: "John", last: "Doe") # calls `new` implicitly
for ref types
echo person1.first, "
Global scope should work as any scope, and call destructors when ending.
> adianv said: why should it be called ? x is global and gets never out of
> scope.
The whole point on RAII is to be abble to bind the lifetime of a resource to
the lifetime of an object, to make sure the resource is
> SJW cancer
Can you point to some examples of this in the Rust community? As far as my
experience goes, the Rust community has been nothing but great so I'm curious
what you're referring to.
* * *
@libman that is a nice essay. Thank you for taking the time to write it up.
Sadly I cannot
Indeed, those high priority bugs have in fact been marked that way because they
are breaking changes (in particular the issues labelled stdlib and high
priority). Dealing with them is a must for v0.18.0 and thus by extension v1.0.
So do help us out
> I predict that soon Nim will compile to DNA, subatomic particles, music
> videos, sexual fantasies, and even tactless bizarre forum rants that go on
> and on and don't really have a point...
Don't mistake Nim for Haxe : P
As of today, this is the most reliable source of pending tasks
[https://github.com/nim-lang/Nim/blob/devel/todo.txt](https://github.com/nim-lang/Nim/blob/devel/todo.txt):
version 1.0 battle plan
===
- let 'doAssert' analyse the expressions and
> Either way, financial donations definitely help.
Yup, signed up on BountySource last night.
> What if 0.9.2 was really 1.0 but no one noticed?
I understand that these numbers are arbitrary and there is nothing about a v1.0
release number that suddenly magically bestows anything on the actual software
itself.
My question was in part prompted by comments I saw on /. in earlier articles
> Make this number go under 1000
Thanks for pointing this out. I think it is a good place for me to start.
In my past experience I have found that one of the best ways to learn a new
code base is by tracking down obvious bugs wherein things crash.
It gives you a specific target to aim for and
> What do you mean under term older technologies?
For the first couple of programming jobs I had I literally had physical wyse60
and vt100 terminals sitting on my desk, connected up via 9600 baud (or 19200 if
I was lucky) serial lines.
I have an interest in lexing and parsing and tended to
Our caveman ancestors had this silly belief that a tool should "do one thing
and do it well"...
But then came Nim!
_Nim does everything!_
It slices, it dices, it generates code that generates code that generates
code...
Write a kernel in Nim. Write your Web client-side in Nim. Earlier today
Yeah, I can't seem to resist responding to a mention of Rust's "SJW cancer"
with a pent-up rant about politics in free software ecosystems... (The GitHub
situation has been particularly traumatic...)
I agree about Nim's technical merits. There's something about the "just works"
qualification
You read waay more into my original post than I was intending. TBH I posted
that after a couple of beers and perhaps wasn't being as clear as I could have
been.
The 'it just works' I was referring to was pretty much just the compiler, the
libraries, and following along with the tutorials.
That is entirely up to Araq.
Everyone (including myself) has been hyping up the idea of [The Great Epic
Version One Point Oh
Release](https://en.wikipedia.org/wiki/Software_versioning#Version_1.0_as_a_milestone),
as if that really requires some rigid standard of achievement. I am starting
to
The original post contains two interesting points that may or may not be
connected. The first point, emphasized by the title, is that it (Nim) "all
'just works'". The second point, mentioned in passing, talks about
dissatisfaction with the political culture in competing projects encouraging
# Idea #1 (Probably not)
Place some sort of guard around fork in the posix module that checks for any
active threads before forking.
There are async-signal-safe routines that can are valid to call post-fork.
Maybe not a good idea to change the expected behavior of the OS-specific fork
18 matches
Mail list logo
