CPS plugin in 2.10

Hi folks,

given that we (Akka) are using the CPS plugin since some time now for a dataflow DSL on top of Futures and that we will use it in adding some of the scala.actors behavior for an easier transition between actor libraries, I would like to ask whether the CPS plugin will be enabled unconditionally in 2.10. The specific reason behind my question is that if it is not enabled, then compiling code against akka-actor.jar will work, but if it calls some Future methods there will be NoSuchMethodErrors, which you’ll agree is not at all desirable.

So, in case there will be any way to run Scalac 2.10 without this transformation, I humbly request that there shall be compiler errors when encountering @cps method signatures.

Regards,

Roland

Re: CPS plugin in 2.10

+1
Eric.

Re: CPS plugin in 2.10

On Sun, Dec 4, 2011 at 9:14 AM, rkuhn wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,

Miles

Re: CPS plugin in 2.10

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <miles [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

--
Miles Sabin
tel: +44 7813 944 528
gtalk: miles [at] milessabin [dot] com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://www.chuusai.com/

Re: CPS plugin in 2.10

A big +1 for the annotation. It's vitally important that code that is written assuming some compiler plugin does indeed get compiled with that plugin enabled. 
Matthew

2011/12/4 √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com>

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <miles [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

--
Miles Sabin
tel: +44 7813 944 528
gtalk: miles [at] milessabin [dot] com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://www.chuusai.com/



--
Dr Matthew PocockIntegrative Bioinformatics Group, School of Computing Science, Newcastle Universitymailto: turingatemyhamster [at] gmail [dot] com gchat: turingatemyhamster [at] gmail [dot] commsn: matthew_pocock [at] yahoo [dot] co [dot] uk irc.freenode.net: drdozerskype: matthew.pococktel: (0191) 2566550mob: +447535664143

Re: CPS plugin in 2.10

+1

On Tue, Dec 6, 2011 at 3:44 AM, Matthew Pocock <turingatemyhamster [at] gmail [dot] com> wrote:
A big +1 for the annotation. It's vitally important that code that is written assuming some compiler plugin does indeed get compiled with that plugin enabled. 
Matthew

2011/12/4 √iktor Ҡlang <viktor [dot] klang [at] gmail [dot] com>

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <miles [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

--
Miles Sabin
tel: +44 7813 944 528
gtalk: miles [at] milessabin [dot] com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://www.chuusai.com/



--
Dr Matthew PocockIntegrative Bioinformatics Group, School of Computing Science, Newcastle University mailto: turingatemyhamster [at] gmail [dot] com gchat: turingatemyhamster [at] gmail [dot] commsn: matthew_pocock [at] yahoo [dot] co [dot] uk irc.freenode.net: drdozerskype: matthew.pococktel: (0191) 2566550mob: +447535664143



--
L.G. Meredith
Managing Partner
Biosimilarity LLC
7329 39th Ave SWSeattle, WA 98136

+1 206.650.3740

http://biosimilarity.blogspot.com

Re: CPS plugin in 2.10

+2

On Dec 4, 2011 2:04 PM, "√iktor Ҡlang" <viktor [dot] klang [at] gmail [dot] com> wrote:

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <miles [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

--
Miles Sabin
tel: +44 7813 944 528
gtalk: miles [at] milessabin [dot] com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://www.chuusai.com/

Re: CPS plugin in 2.10

Yes, yes, yes!
+3 to absolutely everything that's been said on this thread so far :)

On 4 December 2011 20:50, Josh Suereth <joshua [dot] suereth [at] gmail [dot] com> wrote:

+2

On Dec 4, 2011 2:04 PM, "√iktor Ҡlang" <viktor [dot] klang [at] gmail [dot] com> wrote:

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <miles [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

Re: CPS plugin in 2.10

The vote of the “innocent by-standers” is unanimous, now let’s wait for what the “persons concerned” have to add … (I took that phrase from dict.leo.org, hope it’s not out of place ;-) )

Am Sonntag, 4. Dezember 2011 22:56:24 UTC+1 schrieb Kevin Wright:
Yes, yes, yes!
+3 to absolutely everything that's been said on this thread so far :)

On 4 December 2011 20:50, Josh Suereth <joshua [dot] [dot] [dot] [dot] [at] gmail [dot] com> wrote:

+2

On Dec 4, 2011 2:04 PM, "√iktor Ҡlang" <viktor [dot] [dot] [dot] [at] gmail [dot] com> wrote:

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <mi [dot] [dot] [dot] [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <goo [dot] [dot] [dot] [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles

Re: CPS plugin in 2.10

Who are you calling "innocent"?  :)


On 4 December 2011 22:04, rkuhn <google [at] rkuhn [dot] info> wrote:
The vote of the “innocent by-standers” is unanimous, now let’s wait for what the “persons concerned” have to add … (I took that phrase from dict.leo.org, hope it’s not out of place ;-) )

Am Sonntag, 4. Dezember 2011 22:56:24 UTC+1 schrieb Kevin Wright:
Yes, yes, yes!
+3 to absolutely everything that's been said on this thread so far :)

On 4 December 2011 20:50, Josh Suereth <joshua [dot] [dot] [dot] [dot] [at] gmail [dot] com> wrote:

+2

On Dec 4, 2011 2:04 PM, "√iktor Ҡlang" <viktor [dot] [dot] [dot] [at] gmail [dot] com> wrote:

Could we please add a meta annotation named "requireCompilerPlugin("name")

so the compiler barfs?

cheers,
V

On Dec 4, 2011 5:56 PM, "Miles Sabin" <mi [dot] [dot] [dot] [at] milessabin [dot] com> wrote:
On Sun, Dec 4, 2011 at 9:14 AM, rkuhn <goo [dot] [dot] [dot] [at] rkuhn [dot] info> wrote:
> given that we (Akka) are using the CPS plugin since some time now for a
> dataflow DSL on top of Futures and that we will use it in adding some of the
> scala.actors behavior for an easier transition between actor libraries, I
> would like to ask whether the CPS plugin will be enabled unconditionally in
> 2.10. The specific reason behind my question is that if it is not enabled,
> then compiling code against akka-actor.jar will work, but if it calls some
> Future methods there will be NoSuchMethodErrors, which you’ll agree is not
> at all desirable.
>
> So, in case there will be any way to run Scalac 2.10 without this
> transformation, I humbly request that there shall be compiler errors when
> encountering @cps method signatures.

Yes, please let's have this enabled by default.

Cheers,


Miles



Re: CPS plugin in 2.10

+1 for enabling it by default.

On Sun, Dec 4, 2011 at 4:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
Hi folks,

given that we (Akka) are using the CPS plugin since some time now for a dataflow DSL on top of Futures and that we will use it in adding some of the scala.actors behavior for an easier transition between actor libraries, I would like to ask whether the CPS plugin will be enabled unconditionally in 2.10. The specific reason behind my question is that if it is not enabled, then compiling code against akka-actor.jar will work, but if it calls some Future methods there will be NoSuchMethodErrors, which you’ll agree is not at all desirable.

So, in case there will be any way to run Scalac 2.10 without this transformation, I humbly request that there shall be compiler errors when encountering @cps method signatures.

Regards,

Roland

Re: CPS plugin in 2.10

+1 :-)

On Dec 4, 2011 2:44 PM, "Josh Suereth" <joshua [dot] suereth [at] gmail [dot] com> wrote:
+1 for enabling it by default.

On Sun, Dec 4, 2011 at 4:14 AM, rkuhn <google [at] rkuhn [dot] info> wrote:
Hi folks,

given that we (Akka) are using the CPS plugin since some time now for a dataflow DSL on top of Futures and that we will use it in adding some of the scala.actors behavior for an easier transition between actor libraries, I would like to ask whether the CPS plugin will be enabled unconditionally in 2.10. The specific reason behind my question is that if it is not enabled, then compiling code against akka-actor.jar will work, but if it calls some Future methods there will be NoSuchMethodErrors, which you’ll agree is not at all desirable.

So, in case there will be any way to run Scalac 2.10 without this transformation, I humbly request that there shall be compiler errors when encountering @cps method signatures.

Regards,

Roland

Copyright © 2013 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland