[ 
https://issues.apache.org/jira/browse/AVRO-3479?focusedWorklogId=755440&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-755440
 ]

ASF GitHub Bot logged work on AVRO-3479:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Apr/22 21:10
            Start Date: 11/Apr/22 21:10
    Worklog Time Spent: 10m 
      Work Description: martin-g commented on PR #1631:
URL: https://github.com/apache/avro/pull/1631#issuecomment-1095569243

   > While reading about procedure macros I found 
https://crates.io/crates/darling. I have the feeling it may simplify our derive 
functionality.
   
   I've just pushed 
https://github.com/apache/avro/pull/1631/commits/ff751500db3475170c8f10a946ced67088a648cc
 - it uses Darling to parse the derive attributes.
   I didn't manage to pass the `avro_attrs.doc` to the `quote!()` that 
generates the TokenStream for the Schema :-/ `doc: #doc` didn't work.
   
   Feel free to revert this commit if you don't like it for any reason!
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 755440)
    Time Spent: 2h  (was: 1h 50m)

> [rust] Derive Avro Schema macro
> -------------------------------
>
>                 Key: AVRO-3479
>                 URL: https://issues.apache.org/jira/browse/AVRO-3479
>             Project: Apache Avro
>          Issue Type: Improvement
>            Reporter: Jack Klamer
>            Assignee: Jack Klamer
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> The tracking Issue for the Avro Derive Feature of the rust SDK. 
> Proposal (copied from email):
> Have another rust crate that is importable as a feature on the main crate (in 
> the same manner as serde derive), that will provide a derive proc_macro that 
> implements a simple trait that returns the schema for the implementing type. 
> Right now, schemas must be parsed from strings ( or read from files first), 
> and closely coordinated with the associated struct. This makes sense for 
> workflows that need to associate the same type across languages. For programs 
> that are all within Rust, there are usability advantages of the proc_macro. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to