Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

The netstandard2.0 public surface and dependencies are checked by nothing

未关闭
#1,182 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp

调研方向

从 Sources/AngouriMath/AngouriMath.csproj 和 UnitTests 目标框架配置开始,然后阅读 PublicApi.txt 和 KernelDependenciesTest,以了解当前针对单个 TFM 的检查。以 EverythingBuild.yml 为上下文,比较 netstandard2.0 leg 和当前的 net leg。完成标准是:每个选定的 TFM 都检查其公共 API 和内核依赖项,并分别覆盖 PublicApi.txt。

由索引模型根据 Issue 内容生成。

描述

UnitTests targets net10.0 only, so everything asserted about the public surface and about the
kernel's dependencies is asserted about one of the three target frameworks.

Sources/AngouriMath/AngouriMath.csproj builds netstandard2.0;net8.0;net10.0, and the legs differ
by construction:

  • Core/Serialization is #if NET8_0_OR_GREATER
  • GenericMath is Compile Removed below net7
  • netstandard2.0 carries System.Memory as a package rather than a framework reference

So PublicApi.txt records the net10.0 surface, and the netstandard2.0 public surface is checked by
nothing.
A member could be added to, or removed from, that leg without any test noticing.

This is #783's own objection — "unbuilt configurations rot silently" — arriving through the one
construct that issue permits. It closed as adopted; this is the piece it did not cover.

KernelDependenciesTest (#1181) has the same bound and says so in its own remarks: it asserts the
referenced assemblies of whichever framework UnitTests builds, which is why System.Memory appears
there as a framework reference and the netstandard2.0 package reference is invisible to it.

What would close this

A per-TFM check, and the cheap version is probably enough: multi-target UnitTests (or a small
second test project) at least across netstandard2.0 and the current net, and record one
PublicApi.txt per leg. That also gives KernelDependenciesTest its second column for free.

What is not being claimed

No defect has been observed on the netstandard2.0 leg. The point is that one could not be observed —
EverythingBuild.yml compiles it, which catches a build break, and nothing checks its surface or
its dependencies. Filed because two separate checks have now hit the same bound and both had to
record it as a limitation rather than test it.

主要语言
C#
星标
831
派生
79
平均合并
2 小时 22 分钟
30 天内合并 PR
507

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ASC-Community/AngouriMath 的其他 Issue

查看 ASC-Community/AngouriMath 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。