Checking actors for race freedom

Hi Philipp.

I am very interested in trying this plugin out. But I can't share the
code ATM. Do you have anything worth playing with?

Thanks, Jonas.

2009/3/8 Philipp Haller :
> Hello everybody,
>
> We are currently working on a compiler plug-in that can be used to check
> that actors do not accidentally share mutable state.
>
> The motivation is that in some applications, such as an image processing
> pipeline, it is helpful or even necessary for performance reasons to
> send and receive mutable objects. We have been working on a new
> type-based approach to check that actors remain isolated even in such
> cases. We believe that our approach is quite flexible, but want to
> evaluate our ideas with more practical examples.
>
> So, if you are involved in or know of some project using actors that
> could benefit either from our checker or from mutable message objects
> and whose source code could be made available to us, I'd be happy to
> hear from you.
>
> Thanks,
> Philipp
>
> PS: Even if you don't know of a concrete project, but have a programming
> pattern/example in mind that could be challenging/interesting, don't
> hesitate to let me know!
>

Hi Philipp.

I am very interested in trying this plugin out. But I can't share the
code ATM. Do you have anything worth playing with?

Thanks, Jonas.

2009/3/8 Philipp Haller :
> Hello everybody,
>
> We are currently working on a compiler plug-in that can be used to check
> that actors do not accidentally share mutable state.
>
> The motivation is that in some applications, such as an image processing
> pipeline, it is helpful or even necessary for performance reasons to
> send and receive mutable objects. We have been working on a new
> type-based approach to check that actors remain isolated even in such
> cases. We believe that our approach is quite flexible, but want to
> evaluate our ideas with more practical examples.
>
> So, if you are involved in or know of some project using actors that
> could benefit either from our checker or from mutable message objects
> and whose source code could be made available to us, I'd be happy to
> hear from you.
>
> Thanks,
> Philipp
>
> PS: Even if you don't know of a concrete project, but have a programming
> pattern/example in mind that could be challenging/interesting, don't
> hesitate to let me know!
>

Hi Jonas,

Jonas Bonér wrote:
> I am very interested in trying this plugin out. But I can't share the
> code ATM. Do you have anything worth playing with?

I'd love to get your feedback.
However, my prototype is still a bit rough around the edges, but I hope
to do an alpha release in one or two weeks. Stay tuned.

Cheers,
Philipp

> 2009/3/8 Philipp Haller :
>> Hello everybody,
>>
>> We are currently working on a compiler plug-in that can be used to check
>> that actors do not accidentally share mutable state.
>>
>> The motivation is that in some applications, such as an image processing
>> pipeline, it is helpful or even necessary for performance reasons to
>> send and receive mutable objects. We have been working on a new
>> type-based approach to check that actors remain isolated even in such
>> cases. We believe that our approach is quite flexible, but want to
>> evaluate our ideas with more practical examples.
>>
>> So, if you are involved in or know of some project using actors that
>> could benefit either from our checker or from mutable message objects
>> and whose source code could be made available to us, I'd be happy to
>> hear from you.
>>
>> Thanks,
>> Philipp
>>
>> PS: Even if you don't know of a concrete project, but have a programming
>> pattern/example in mind that could be challenging/interesting, don't
>> hesitate to let me know!
>>
>
>
>

Hi Jonas,

Jonas Bonér wrote:
> I am very interested in trying this plugin out. But I can't share the
> code ATM. Do you have anything worth playing with?

I'd love to get your feedback.
However, my prototype is still a bit rough around the edges, but I hope
to do an alpha release in one or two weeks. Stay tuned.

Cheers,
Philipp

> 2009/3/8 Philipp Haller :
>> Hello everybody,
>>
>> We are currently working on a compiler plug-in that can be used to check
>> that actors do not accidentally share mutable state.
>>
>> The motivation is that in some applications, such as an image processing
>> pipeline, it is helpful or even necessary for performance reasons to
>> send and receive mutable objects. We have been working on a new
>> type-based approach to check that actors remain isolated even in such
>> cases. We believe that our approach is quite flexible, but want to
>> evaluate our ideas with more practical examples.
>>
>> So, if you are involved in or know of some project using actors that
>> could benefit either from our checker or from mutable message objects
>> and whose source code could be made available to us, I'd be happy to
>> hear from you.
>>
>> Thanks,
>> Philipp
>>
>> PS: Even if you don't know of a concrete project, but have a programming
>> pattern/example in mind that could be challenging/interesting, don't
>> hesitate to let me know!
>>
>
>
>

Sounds good. Thanks.

2009/3/24 Philipp Haller :
> Hi Jonas,
>
> Jonas Bonér wrote:
>>
>> I am very interested in trying this plugin out. But I can't share the
>> code ATM. Do you have anything worth playing with?
>
> I'd love to get your feedback.
> However, my prototype is still a bit rough around the edges, but I hope to
> do an alpha release in one or two weeks. Stay tuned.
>
> Cheers,
> Philipp
>
>
>> 2009/3/8 Philipp Haller :
>>>
>>> Hello everybody,
>>>
>>> We are currently working on a compiler plug-in that can be used to check
>>> that actors do not accidentally share mutable state.
>>>
>>> The motivation is that in some applications, such as an image processing
>>> pipeline, it is helpful or even necessary for performance reasons to
>>> send and receive mutable objects. We have been working on a new
>>> type-based approach to check that actors remain isolated even in such
>>> cases. We believe that our approach is quite flexible, but want to
>>> evaluate our ideas with more practical examples.
>>>
>>> So, if you are involved in or know of some project using actors that
>>> could benefit either from our checker or from mutable message objects
>>> and whose source code could be made available to us, I'd be happy to
>>> hear from you.
>>>
>>> Thanks,
>>> Philipp
>>>
>>> PS: Even if you don't know of a concrete project, but have a programming
>>> pattern/example in mind that could be challenging/interesting, don't
>>> hesitate to let me know!
>>>
>>
>>
>>
>
>

Sounds good. Thanks.

2009/3/24 Philipp Haller :
> Hi Jonas,
>
> Jonas Bonér wrote:
>>
>> I am very interested in trying this plugin out. But I can't share the
>> code ATM. Do you have anything worth playing with?
>
> I'd love to get your feedback.
> However, my prototype is still a bit rough around the edges, but I hope to
> do an alpha release in one or two weeks. Stay tuned.
>
> Cheers,
> Philipp
>
>
>> 2009/3/8 Philipp Haller :
>>>
>>> Hello everybody,
>>>
>>> We are currently working on a compiler plug-in that can be used to check
>>> that actors do not accidentally share mutable state.
>>>
>>> The motivation is that in some applications, such as an image processing
>>> pipeline, it is helpful or even necessary for performance reasons to
>>> send and receive mutable objects. We have been working on a new
>>> type-based approach to check that actors remain isolated even in such
>>> cases. We believe that our approach is quite flexible, but want to
>>> evaluate our ideas with more practical examples.
>>>
>>> So, if you are involved in or know of some project using actors that
>>> could benefit either from our checker or from mutable message objects
>>> and whose source code could be made available to us, I'd be happy to
>>> hear from you.
>>>
>>> Thanks,
>>> Philipp
>>>
>>> PS: Even if you don't know of a concrete project, but have a programming
>>> pattern/example in mind that could be challenging/interesting, don't
>>> hesitate to let me know!
>>>
>>
>>
>>
>
>