Pastey crate requirement#33
Conversation
bharatGoswami8
commented
May 11, 2026
bharatGoswami8
commented
- System requirement
- Feature requirement
- Component requirement
bharatGoswami8
force-pushed
the
pastey_requirement
branch
3 times, most recently
from
94e6dbf to
de54bc5
Compare
* System requirement * Feature requirement * Component requirement
bharatGoswami8
force-pushed
the
pastey_requirement
branch
from
de54bc5 to
d49d161
Compare
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comments
| import ScoreReq | ||
|
|
||
| ScoreReq.AssumedSystemReq ASR_PASTEY_001 { | ||
| description = "The Rust compiler shall support procedural macro invocation that transforms token streams at compile time, including accepting raw identifiers (r#ident) and #[doc = ...] attribute tokens emitted from a procedural macro as syntactically valid output" |
There was a problem hiding this comment.
Wrong understanding of assumed System Requirements: it does not describe the assumption of what the system (here the Rust compiler, which is not part of our SW platform) would provide for your component/crate but what you think the system expects from "paste! macro". These would be "Assumptions of Use" and I think be documented in the feature requirements trlc. And it should be on a level like https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__dev_experience__prog_languages (from user of the platform perspective).
There was a problem hiding this comment.
I have updated system requirement in term of Rust toolchain which is kind of external system.
There was a problem hiding this comment.
need to discuss this
There was a problem hiding this comment.
Agreed in meeting to replace these by a assumed system requirment like https://eclipse-score.github.io/score/main/requirements/stakeholder/index.html#stkh_req__dev_experience__prog_languages and to create an AoU on feature level stating that pastey crate expects "qualified Rust compiler including macro infrastructure". AoU in trlc: see https://github.com/eclipse-score/communication/blob/main/score/mw/com/dependability/safety_analysis/aou.trlc
bharatGoswami8
force-pushed
the
pastey_requirement
branch
from
b393ca8 to
e0b5bee
Compare
aschemmel-tech
left a comment
aschemmel-tech
left a comment
There was a problem hiding this comment.
see still open and new inline comments
There was a problem hiding this comment.
Discussed in meeting: our preferred solution was to have one feature collecting several crates (components) - which would mean that the feature level requirements could be even more abstract. Folder structure can be kept.
2 participants
