[
https://issues.apache.org/jira/browse/AVRO-3479?focusedWorklogId=755358&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-755358
]
ASF GitHub Bot logged work on AVRO-3479:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Apr/22 18:09
Start Date: 11/Apr/22 18:09
Worklog Time Spent: 10m
Work Description: martin-g commented on PR #1631:
URL: https://github.com/apache/avro/pull/1631#issuecomment-1095376480
@jklamer While reading about procedure macros I found
https://crates.io/crates/darling. I have the feeling it may simplify our derive
functionality.
Issue Time Tracking
-------------------
Worklog Id: (was: 755358)
Time Spent: 1.5h (was: 1h 20m)
> [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: 1.5h
> 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)
