[
https://issues.apache.org/jira/browse/AVRO-3479?focusedWorklogId=757396&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757396
]
ASF GitHub Bot logged work on AVRO-3479:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/22 13:30
Start Date: 15/Apr/22 13:30
Worklog Time Spent: 10m
Work Description: martin-g commented on PR #1631:
URL: https://github.com/apache/avro/pull/1631#issuecomment-1100111669
Yes, packaging is not easy! :-)
I just tried strum project and it fails the same way.
The way https://github.com/TedDriggs/darling is structured supports it
though!
Here the main project is both a lib (it has ./src/lib.rs) and it is also a
workspace with a -core and -macro subprojects.
Issue Time Tracking
-------------------
Worklog Id: (was: 757396)
Time Spent: 2h 50m (was: 2h 40m)
> [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 50m
> 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)
