openharmony/third_party_rust_quote
1
0
Fork 0
mirror of https://github.com/openharmony/third_party_rust_quote.git synced 2026-07-01 20:44:02 -04:00
Code Issues Packages Projects Releases Wiki Activity
558 Commits 226 Branches 29 Tags
master
Commit Graph

558 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
openharmony_ci 0a3ca249aa !17 merge master into master 
README.OpenSource修改

Created-by: dragonswordy
Commit-by: ljy9810
Merged-by: openharmony_ci
Description: ### 一、内容说明（相关的Issue）
https://gitcode.com/openharmony/third_party_rust_unicode-ident/issues/3


### 二、建议测试周期和提测地址  
  建议测试完成时间：xxxx.xx.xx  
  投产上线时间：xxxx.xx.xx  
  提测地址：CI环境/压测环境  
  测试账号：  

### 三、变更内容
  * 3.1 关联PR列表

  * 3.2 数据库和部署说明  
    1. 常规更新 
    2. 重启unicorn
    3. 重启sidekiq
    4. 迁移任务：是否有迁移任务，没有写 "无"
    5. rake脚本：`bundle exec xxx RAILS_ENV = production`；没有写 "无"

  * 3.4 其他技术优化内容（做了什么，变更了什么）
    - 重构了 xxxx 代码
    - xxxx 算法优化


  * 3.5 废弃通知（什么字段、方法弃用？）



  * 3.6  后向不兼容变更（是否有无法向后兼容的变更？）


  
### 四、研发自测点（自测哪些？冒烟用例全部自测？）
  自测测试结论：


### 五、测试关注点（需要提醒QA重点关注的、可能会忽略的地方）
  检查点：

| 需求名称 | 是否影响xx公共模块 | 是否需要xx功能 | 需求升级是否依赖其他子产品 |
|------|------------|----------|---------------|
| xxx  | 否          | 需要       | 不需要           |
|      |            |          |               |

  接口测试：

  性能测试：

  并发测试：

  其他：



See merge request: openharmony/third_party_rust_quote!17
OpenHarmony-v7.0-Beta1 		2026-04-09 20:56:05 +08:00
ljy9810 15359c51c6 README.OpenSource修改 
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
 2026-04-09 17:50:39 +08:00
openharmony_ci 893c510d22 !16 merge master into master 
quote版本升级到1.0.43

Created-by: dragonswordy
Commit-by: ljy9810
Merged-by: openharmony_ci
Description: ### 一、内容说明（相关的Issue）
https://gitcode.com/openharmony/third_party_rust_unicode-ident/issues/2


### 二、建议测试周期和提测地址  
  建议测试完成时间：xxxx.xx.xx  
  投产上线时间：xxxx.xx.xx  
  提测地址：CI环境/压测环境  
  测试账号：  

### 三、变更内容
  * 3.1 关联PR列表

  * 3.2 数据库和部署说明  
    1. 常规更新 
    2. 重启unicorn
    3. 重启sidekiq
    4. 迁移任务：是否有迁移任务，没有写 "无"
    5. rake脚本：`bundle exec xxx RAILS_ENV = production`；没有写 "无"

  * 3.4 其他技术优化内容（做了什么，变更了什么）
    - 重构了 xxxx 代码
    - xxxx 算法优化


  * 3.5 废弃通知（什么字段、方法弃用？）



  * 3.6  后向不兼容变更（是否有无法向后兼容的变更？）


  
### 四、研发自测点（自测哪些？冒烟用例全部自测？）
  自测测试结论：


### 五、测试关注点（需要提醒QA重点关注的、可能会忽略的地方）
  检查点：

| 需求名称 | 是否影响xx公共模块 | 是否需要xx功能 | 需求升级是否依赖其他子产品 |
|------|------------|----------|---------------|
| xxx  | 否          | 需要       | 不需要           |
|      |            |          |               |

  接口测试：

  性能测试：

  并发测试：

  其他：



See merge request: openharmony/third_party_rust_quote!16
 2026-03-18 18:59:10 +08:00
ljy9810 04418f59da quote版本升级到1.0.43 
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
 2026-03-03 15:14:49 +08:00
openharmony_ci f432860dbf !13 merge master into master 
quote新增bundle.json部件化

Created-by: dragonswordy
Commit-by: ljy9810
Merged-by: openharmony_ci
Description: ### 一、内容说明（相关的Issue）
https://gitcode.com/openharmony/third_party_rust_autocfg/issues/3


### 二、建议测试周期和提测地址  
  建议测试完成时间：xxxx.xx.xx  
  投产上线时间：xxxx.xx.xx  
  提测地址：CI环境/压测环境  
  测试账号：  

### 三、变更内容
  * 3.1 关联PR列表

  * 3.2 数据库和部署说明  
    1. 常规更新 
    2. 重启unicorn
    3. 重启sidekiq
    4. 迁移任务：是否有迁移任务，没有写 "无"
    5. rake脚本：`bundle exec xxx RAILS_ENV = production`；没有写 "无"

  * 3.4 其他技术优化内容（做了什么，变更了什么）
    - 重构了 xxxx 代码
    - xxxx 算法优化


  * 3.5 废弃通知（什么字段、方法弃用？）



  * 3.6  后向不兼容变更（是否有无法向后兼容的变更？）


  
### 四、研发自测点（自测哪些？冒烟用例全部自测？）
  自测测试结论：


### 五、测试关注点（需要提醒QA重点关注的、可能会忽略的地方）
  检查点：

| 需求名称 | 是否影响xx公共模块 | 是否需要xx功能 | 需求升级是否依赖其他子产品 |
|------|------------|----------|---------------|
| xxx  | 否          | 需要       | 不需要           |
|      |            |          |               |

  接口测试：

  性能测试：

  并发测试：

  其他：



See merge request: openharmony/third_party_rust_quote!13
OpenHarmony-v6.1-Release 		2025-12-31 22:05:19 +08:00
ljy9810 b99c87566a quote新增bundle.json部件化 
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
 2025-12-11 15:46:22 +08:00
openharmony_ci e789092da9 merge master into master 
升级到1.0.37

Created-by: dragonswordy
Commit-by: ljy9810
Merged-by: openharmony_ci
Description: ### 一、内容说明（相关的Issue）
https://gitcode.com/openharmony/third_party_rust_memoffset/issues/1


### 二、建议测试周期和提测地址  
  建议测试完成时间：xxxx.xx.xx  
  投产上线时间：xxxx.xx.xx  
  提测地址：CI环境/压测环境  
  测试账号：  

### 三、变更内容
  * 3.1 关联PR列表

  * 3.2 数据库和部署说明  
    1. 常规更新 
    2. 重启unicorn
    3. 重启sidekiq
    4. 迁移任务：是否有迁移任务，没有写 "无"
    5. rake脚本：`bundle exec xxx RAILS_ENV = production`；没有写 "无"

  * 3.4 其他技术优化内容（做了什么，变更了什么）
    - 重构了 xxxx 代码
    - xxxx 算法优化


  * 3.5 废弃通知（什么字段、方法弃用？）



  * 3.6  后向不兼容变更（是否有无法向后兼容的变更？）


  
### 四、研发自测点（自测哪些？冒烟用例全部自测？）
  自测测试结论：


### 五、测试关注点（需要提醒QA重点关注的、可能会忽略的地方）
  检查点：

| 需求名称 | 是否影响xx公共模块 | 是否需要xx功能 | 需求升级是否依赖其他子产品 |
|------|------------|----------|---------------|
| xxx  | 否          | 需要       | 不需要           |
|      |            |          |               |

  接口测试：

  性能测试：

  并发测试：

  其他：



See merge request: openharmony/third_party_rust_quote!11
 2025-09-01 20:25:37 +08:00
ljy9810 b01f68b2e8 升级到1.0.37 
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
 2025-09-01 16:57:49 +08:00
openharmony_ci aad08de19f !6 修改软件名 
Merge pull request !6 from 李可/master
OpenHarmony-v6.0-Beta1 OpenHarmony-v5.1.0-Release 		2024-09-29 07:08:41 +00:00
李可 61efa1e919 update README.OpenSource 
Signed-off-by: 李可 <like115@huawei.com>
 2024-09-27 10:47:57 +00:00
openharmony_ci 1e41d82ab2 !5 quote1.0.23升级至1.0.35 
Merge pull request !5 from Future/new1
OpenHarmony-v5.0-Beta1 		2024-04-08 15:02:36 +00:00
徐未来 d71ef629b7 1.0.23升级至1.0.35 
Signed-off-by: 徐未来 <xuweilai2@huawei.com>
 2024-04-02 17:14:42 +08:00
openharmony_ci 9886415a01 !4 回退 'Pull Request !3 : quote1.0.23升级至1.0.35' 
Merge pull request !4 from openharmony_ci/revert-merge-3-master
 2024-04-02 03:39:55 +00:00
openharmony_ci fa024de82c 回退 'Pull Request !3 : quote1.0.23升级至1.0.35' 2024-04-02 03:33:02 +00:00
openharmony_ci 5adbcdfa68 !3 quote1.0.23升级至1.0.35 
Merge pull request !3 from Future/master
 2024-04-02 01:45:05 +00:00
徐未来 8a30c88502 1.0.23升级至1.0.35 
Signed-off-by: 徐未来 <xuweilai2@huawei.com>
 2024-03-11 18:55:48 +08:00
openharmony_ci d059e4f579 !2 Add OAT.xml and README.OpenSource 
Merge pull request !2 from fangting/master
OpenHarmony-v4.1.4-Release OpenHarmony-v4.1.3-Release OpenHarmony-v4.1.2-Release OpenHarmony-v4.0.4-Release OpenHarmony-v4.0.3-Release OpenHarmony-v4.0.2-Release OpenHarmony-v4.0-Beta1 OpenHarmony-v4.0-Beta2 OpenHarmony-v4.0-Release OpenHarmony-v4.0.1-Release OpenHarmony-v4.1-Beta1 OpenHarmony-v4.1-Release OpenHarmony-v4.1.1-Release master-v weekly_20240115-v 		2023-04-14 08:11:25 +00:00
fangting b39998d38e Add OAT.xml and README.OpenSource 
Signed-off-by: fangting <fangting12@huawei.com>
 2023-04-14 14:15:20 +08:00
openharmony_ci 30ae8b2e4b !1 [quote]Add GN Build Files and Custom Modifications to Rust Third-party Libraries 
Merge pull request !1 from lubinglun/master
 2023-04-13 11:33:41 +00:00
lubinglun 9251217d6e Add GN Build Files and Custom Modifications 
Issue:https://gitee.com/openharmony/build/issues/I6UFTP
Signed-off-by: lubinglun <lubinglun@huawei.com>
 2023-04-12 17:26:45 +08:00
David Tolnay 39cf3dd39e Release 1.0.23 github.com/dtolnay/quote/1.0.23 github.com/dtolnay/quote.git/1.0.23 2022-12-18 09:27:50 -08:00
David Tolnay 3206c7e4de Opt out -Zrustdoc-scrape-examples on docs.rs 
I'd like a chance to audit all the code that rustdoc is inserting into
the docs. Currently I am skeptical that showing quote's internal usages
of APIs is a net benefit to the public documentation. I am also
skeptical that quite so many examples are needed, and that they should
be featured so prominently in comparison to handwritten docs. Lastly I
wish there were a way to turn this behavior off on a more granular
basis.
 2022-12-18 09:27:08 -08:00
David Tolnay 8542ced993 Release 1.0.22 2022-12-17 11:32:41 -08:00
David Tolnay 466751adf3 Update build status badge 2022-12-15 17:52:42 -08:00
David Tolnay d71ab0ac28 Update ui test suite to nightly-2022-12-15 2022-12-14 19:09:18 -08:00
David Tolnay d65d6eaf3f Time out workflows after 45 minutes 
GitHub's default timeout is 6 hours. Recently some of my GitHub Actions
jobs have started randomly stalling for that long, which is inconvenient
because it ties up a chunk of my runner quota. It apepars to be very
rare for a job to recover after stalling. It's better to time out
quicker and retry on a different runner.
 2022-11-25 18:56:18 -08:00
David Tolnay 9bef2a0eef Fix renamed let_underscore_drop lint 
warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop`
     --> tests/test.rs:3:5
      |
    3 |     clippy::let_underscore_drop,
      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop`
      |
      = note: `#[warn(renamed_and_removed_lints)]` on by default
 2022-11-22 19:19:40 -08:00
David Tolnay 63d4872eda MIT copyright line 
Delete the first paragraph of LICENSE-MIT (an inaccurate
pseudo-copyright line), leaving only the text of the MIT license.

Nothing about the license of quote has changed, only our understanding
of how to correctly communicate that license has changed.

This mirrors an equivalent chagne applied in the rust-lang/rust
repository years ago.
 2022-10-18 01:52:32 -07:00
David Tolnay e9b8f1cc59 Ui test changes for trybuild 1.0.66 2022-10-04 22:26:34 -07:00
David Tolnay 4331a79e3a Raise minimum tested toolchain to rust 1.56 
Required by the transitive dev-dependency on once_cell.

    error: failed to parse manifest at github.com-1ecc6299db9ec823/once_cell-1.15.0/Cargo.toml

    Caused by:
      feature `edition2021` is required

      The package requires the Cargo feature called `edition2021`, but that feature is not stabilized in this version of Cargo (1.55.0 (32da73ab1 2021-08-23)).
      Consider trying a newer version of Cargo (this may require the nightly release).
      See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2021 for more information about the status of this feature.
 2022-09-20 22:26:55 -07:00
David Tolnay 709b9e7241 Remove default package.readme metadata from Cargo.toml 
Since cargo 1.46.0, README.md is recognized by default.
 2022-09-14 09:16:00 -07:00
David Tolnay 572bf1baf8 GitHub Workflows security hardening 2022-09-02 15:09:30 -07:00
David Tolnay befeac0626 Ignore using destructuring assignment to wildcard pattern 2022-08-31 00:29:08 -07:00
David Tolnay b92dc7aeed Update ui test suite to nightly-2022-08-23 2022-08-22 23:05:12 -07:00
David Tolnay acf90ab43e Update ui test suite to nightly-2022-08-20 2022-08-19 21:38:42 -07:00
David Tolnay b0f7024526 Resolve renamed_and_removed_lints warning on blacklisted_name 
warning: lint `clippy::blacklisted_name` has been renamed to `clippy::disallowed_names`
     --> tests/test.rs:2:5
      |
    2 |     clippy::blacklisted_name,
      |     ^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `clippy::disallowed_names`
      |
      = note: `#[warn(renamed_and_removed_lints)]` on by default
 2022-08-12 21:37:38 -07:00
David Tolnay a13b596dad Release 1.0.21 2022-08-02 20:58:15 -07:00
David Tolnay 0c25eb7ce1 Update keywords in crates.io metadata 2022-08-02 10:38:56 -07:00
David Tolnay 71437043ea Change std imports to core where possible 
Useful for seeing what are the gaps toward being compatible with
no-std. Useful for copying chunks of code into a no-std crate.
 2022-07-31 23:05:17 -07:00
David Tolnay 704fc30810 Sort package entries in Cargo.toml 2022-07-31 19:19:04 -07:00
David Tolnay 0b07fad30b Update ui test suite to nightly-2022-07-28 2022-07-27 21:03:20 -07:00
David Tolnay 340ebea4ee Update ui test suite to nightly-2022-07-20 2022-07-19 21:21:18 -07:00
David Tolnay 713f9aa2ac Update ui test suite to nightly-2022-07-10 2022-07-09 19:50:03 -07:00
David Tolnay f9401ac58c Update ui test suite to nightly-2022-07-02 2022-07-01 20:02:56 -07:00
David Tolnay 56f99d583a Use dtolnay/rust-toolchain's miri toolchain 
This defaults to components miri + rust-src.
 2022-06-29 10:56:00 -07:00
David Tolnay dc44c50628 Update ui test suite to nightly-2022-06-26 2022-06-25 22:54:51 -07:00
David Tolnay 9fd7dcefad Release 1.0.20 2022-06-19 19:14:08 -07:00
David Tolnay a811a8c6af Hygienic path for ::std::option::Option 2022-06-19 19:13:42 -07:00
David Tolnay f9a910074d Merge pull request #226 from dtolnay/format 
Call `format!` through an unambiguous path
 2022-06-19 19:12:11 -07:00
David Tolnay 2eeda76c6f Call 'format!' through an unambiguous path 
Repro:

    use quote::format_ident;

    macro_rules! format {
        () => {};
    }

    fn main() {
        let _ = format_ident!("foo");
    }

Previously:

    error: no rules expected the token `"foo"`
     --> src/main.rs:8:13
      |
    3 | macro_rules! format {
      | ------------------- when calling this macro
    ...
    8 |     let _ = format_ident!("foo");
      |             ^^^^^^^^^^^^^^^^^^^^ no rules expected this token in macro call
      |
      = note: this error originates in the macro `format_ident` (in Nightly builds, run with -Z macro-backtrace for more info)
 2022-06-19 19:06:18 -07:00