Re: [rust-dev] 3 SF events in June: a Dinner, Game Tech Meetup, and a Spinning Trianglthon

2014-06-25 Thread Erick Tryzelaar
Hello rustangles!

Just a friendly reminder that we have a great meetup lined up tomorrow in
San Francisco. Instructions on attending or watching remotely are found
here:

http://www.meetup.com/Rust-Bay-Area/events/17672/

See you tomorrow!
-Erick



On Sat, May 24, 2014 at 8:03 PM, Tom Park  wrote:

> > https://air.mozilla.org/search/?q=rust+meetup
>
> Removing "meetup" from that search might be a little better:
> https://air.mozilla.org/search/?q=rust
>
> Specifically, it yields the Nov 2013 Rust meetup (which includes Yehuda
> Katz's talk about calling Rust from Ruby via C FFI):
> https://air.mozilla.org/sprocketnes-practical-systems-programming-in-rust/
>
> I mention this because about a month ago on #rust IRC, someone was looking
> for that particular talk but having trouble finding it because he was using
> the "meetup" keyword.
>
>
>
> On Thu, May 22, 2014 at 1:52 AM, Jordi Boggiano 
> wrote:
>
>> Here is a link to watch all past (and upcoming) rust meetups for those
>> that can't be there in person. It took me 5min to dig it up again so I
>> thought I'd share.
>>
>> https://air.mozilla.org/search/?q=rust+meetup
>>
>> Cheers
>>
>> --
>> Jordi Boggiano
>> @seldaek - http://nelm.io/jordi
>> ___
>> Rust-dev mailing list
>> Rust-dev@mozilla.org
>> https://mail.mozilla.org/listinfo/rust-dev
>>
>
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
>
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Integer overflow, round -2147483648

2014-06-25 Thread Florian Zeitz
On 26.06.2014 00:04, Vadim Chugunov wrote:
> I wasn't thinking of subtyping u32w to u32.  I actually don't think that
> u32 should be convertible to u32w (or vice-versa) without an explicit
> cast.   For array slices, it would have to be a transmute-like function,
> e.g. fn as_wrapping<'a>(s:&'a [u32])->&'a [u32w] { unsafe { transmute(s) } }
> 
> 
FWIW, as I understand it RFC PR #91
 would nicely deal with such
cases, by making `u32` and `u32w` coercible. I don't think there is any
reason for `u32w` not to be just a newtype of `u32` with appropriate
arithmetic trait impls.
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Integer overflow, round -2147483648

2014-06-25 Thread Vadim Chugunov
I wasn't thinking of subtyping u32w to u32.  I actually don't think that
u32 should be convertible to u32w (or vice-versa) without an explicit
cast.   For array slices, it would have to be a transmute-like function,
e.g. fn as_wrapping<'a>(s:&'a [u32])->&'a [u32w] { unsafe { transmute(s) } }
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Integer overflow, round -2147483648

2014-06-25 Thread Jerry Morrison
On Tue, Jun 24, 2014 at 6:06 PM, Vadim Chugunov  wrote:
>
> On Tue, Jun 24, 2014 at 5:41 PM, Daniel Micay 
>> wrote:
>>
>>> On 24/06/14 08:39 PM, Vadim Chugunov wrote:
>>> > I mostly agree, though  for #1, I think that new int types would be
>>> more
>>> > appropriate.   A set of special operators seems like an overkill for a
>>> > relatively infrequently used functionality.  Annotations are too broad
>>> > (what if I need to do both wrapping and non-wrapping calculations in
>>> the
>>> > same scope?).
>>>
>>> Introducing new types would make the language more painful to use, and
>>> it would be difficult to determine the correct types to use at API
>>> boundaries. It would be a large backwards compatibility hazard among
>>> other issues, and would introduce performance overhead due to issues
>>> like `&[u32]` and `&[u32c]` being different types.
>>
>>
> Easy: don't use normal ints in the API, Cast to wrapping ints when
> needed.I don't expect the slice scenario to come up often, but if it
> does, these slice types can be transmuted into each other.
>

I'm hoping for illumination on that last point from someone who understands
the type system. If, say, u32w subtypes u32, then a u32w collection would
not be assignable to/from a u32 collection. It's the
covariant/contravariant mess. [Mathematicians don't pick understandable
names like "visitor pattern."]

-- 
   Jerry
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Compiling Rust apps with Meson v2

2014-06-25 Thread Jussi Pakkanen
On Wed, Jun 25, 2014 at 1:25 PM, Robert Knight 
wrote:


> Thanks. meson looks like CMake with a somewhat more sane build config
> language. Not directly related to Rust, but what is the tooling story
> like with Qt Creator - eg. has any work been done on teaching Qt
> Creator to understand meson projects?


One of my design principles has been "like CMake but with a saner syntax"
so I'm glad it's showing through. :)

I did have some discussion with Qt Creator guys and as a result made Meson
extremely easy to embed into any IDE, not just QtCreator. Here's the
documentation on that:

https://github.com/jpakkane/meson/wiki/IDE%20integration

Unfortunately the QtC guys are very busy and did not have time to create
the integration bits.

To tie this into Rust, if someone wants to create a Rust IDE with build
system integration (compile, unit tests, debugging said unit tests etc) and
they already have an editor component, integrating Meson is just a matter
of parsing a few simple JSON documents.
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev


Re: [rust-dev] Compiling Rust apps with Meson v2

2014-06-25 Thread Robert Knight
Hi Jussi,

Thanks. meson looks like CMake with a somewhat more sane build config
language. Not directly related to Rust, but what is the tooling story
like with Qt Creator - eg. has any work been done on teaching Qt
Creator to understand meson projects?

On 23 June 2014 21:00, Jussi Pakkanen  wrote:
> Hi
>
> I finished basic Rust support for the Meson build system. It now supports
> shared and static libraries with full install support and all that. Here's
> the entire build definition for a library and two executables that use it.
>
> 
>
> project('libproject', 'rust')
>
> corelib = shared_library('core', 'core.rs')
> executable('someapp', 'someapp.rs', link_with : corelib)
> executable('otherapp', 'otherapp.rs', link_with : corelib)
>
> 
>
> To try it get Meson trunk: https://github.com/jpakkane/meson
>
> If you try to run the Rust unit tests, note that dependency tracking fails
> because rustc creates invalid dependency files. I filed a bug on that:
> https://github.com/rust-lang/rust/issues/15124
>
> Other random tidbits and questions I was asked:
>
> Could Meson build Rust itself? Possibly, though it probably needs some help
> from Rust specialists. If someone wants to try this, I'll be glad to help.
>
> Can Meson handle complex setups? The most complex thus far has been Qt
> Creator:
>
> http://sourceforge.net/p/meson/mailman/message/32335155/
>
> Enjoy,
>
>
>
> ___
> Rust-dev mailing list
> Rust-dev@mozilla.org
> https://mail.mozilla.org/listinfo/rust-dev
>
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev