destination is described by following enum:
enum AttributeAvailibility {
case SOURCE
case COMPILE
case RUNTIME
}
> On 26 Dec 2015, at 20:31, Radosław Smogura via swift-evolution
> <swift-evolution@swift.org> wrote:
>
>
>> On 26 Dec 2015, at 19:57, JOSE MARIA GOMEZ C
I think that throwing out our effort is bed idea. Waiting for reflection system
may cause that implementation of attributes will be impossible - both of those
things should be done together!
Maybe it would be good to work on agile, iterative bases? What do you think
about defining for MVP
-
Hi,
That’s a great idea!
Kind regards,
Radek
> On 27 Dec 2015, at 21:10, Taras Zakharko via swift-evolution
> wrote:
>
> Quite often, one needs to perform a number of operations on a single object
> (e.g. call up a bunch of configuration or action methods). This
> On 26 Dec 2015, at 19:57, JOSE MARIA GOMEZ CAMA <jm.go...@ub.edu> wrote:
>
> Dear all,
>
> Let me answer inlined.
>
>> El 26/12/2015, a las 19:15, Radosław Smogura via swift-evolution
>> <swift-evolution@swift.org> escribió:
>>
>>
So,
What do you think about syntax like this:
// Declaration
@AttributeUsage(RUNTIME) //Can be SOURCE - attribute not emitted into binary
@AttributeTarget(PROPERTY) //Other CLASS, ENUM, METHOD, INIT
@attribute JSONProperty {
var name:String!;
var serializable:Bool? = true;
var
Hi Dimitir,
Thanks for your questions, as you pointed me to deeper considerations and
better description of idea.
> On 26 Dec 2015, at 16:20, Dmitri Gribenko wrote:
>
> On Sat, Dec 26, 2015 at 3:59 PM, Radosław Smogura wrote:
>> So,
>>
>> What do
Hello Swift Team,
As it’s my first post on this mailing list, let me introduce my self. My name
is Radek Smogura, and for 10 year I work as developer, mainly Java and I know C
and C++. I would like to join Swift community and work on Swift language.
Previously for hobby I added properties