3551 Commits

Author SHA1 Message Date
openharmony_ci 8bcc6c97ed !14 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_syn!14
OpenHarmony-v7.0-Beta1 OpenHarmony-v7.0-Release
2026-04-09 20:56:18 +08:00
ljy9810 8f1986abce README.OpenSource修改
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
2026-04-09 17:44:31 +08:00
openharmony_ci a8ed5e1655 !13 merge master into master
syn升级到2.0.114版本

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_syn!13
2026-03-18 18:59:02 +08:00
ljy9810 b50d6d940a syn升级到2.0.114版本
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
2026-03-03 14:22:30 +08:00
openharmony_ci e64c26b47c !10 merge master into master
syn新增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_syn!10
OpenHarmony-v6.1-Release OpenHarmony-v6.1-LTS
2025-12-31 22:05:51 +08:00
ljy9810 5f6ae1ad9a syn新增bundle.json部件化
Signed-off-by: ljy9810 <longjianyin@h-partners.com>
2025-12-11 16:02:21 +08:00
openharmony_ci 530a833b8b !8 syn 1.0.107升级至2.0.48
Merge pull request !8 from Future/new4
OpenHarmony-v6.0.0.1-Release OpenHarmony-v6.0-Release OpenHarmony-v6.0-Beta1 OpenHarmony-v5.1.0-Release OpenHarmony-v5.0.3-Release OpenHarmony-v5.0.2-Release OpenHarmony-v5.0.1-Release OpenHarmony-v5.0.0-Release OpenHarmony-v5.0-Beta1 OpenHarmony-v6.0.0.2-Release
2024-04-08 15:02:37 +00:00
徐未来 24b56b7a55 syn 1.0.107升级至2.0.48
Signed-off-by: 徐未来 <xuweilai2@huawei.com>
2024-04-02 16:51:27 +08:00
openharmony_ci 987cdb51c2 !7 回退 'Pull Request !6 : syn 1.0.107升级至2.0.48'
Merge pull request !7 from openharmony_ci/revert-merge-6-master
2024-04-02 03:39:29 +00:00
openharmony_ci 5496fdbd4c 回退 'Pull Request !6 : syn 1.0.107升级至2.0.48' 2024-04-02 03:27:54 +00:00
openharmony_ci c4c1ee1bc3 !6 syn 1.0.107升级至2.0.48
Merge pull request !6 from Future/new1
2024-04-02 01:45:08 +00:00
徐未来 a83871dba6 syn 1.0.107升级至2.0.48
Signed-off-by: 徐未来 <xuweilai2@huawei.com>
2024-04-01 20:47:12 +08:00
openharmony_ci 51011a34f4 !5 回退 'Pull Request !4 : syn 1.0.107升级至2.0.48'
Merge pull request !5 from openharmony_ci/revert-merge-4-master
2024-04-01 12:17:24 +00:00
openharmony_ci b23f93737f 回退 'Pull Request !4 : syn 1.0.107升级至2.0.48' 2024-04-01 12:11:54 +00:00
hhj 740fc54f29 !4 syn 1.0.107升级至2.0.48
Merge pull request !4 from Future/master
2024-04-01 11:31:37 +00:00
徐未来 38de391e34 syn 1.0.107升级至2.0.48
Signed-off-by: 徐未来 <xuweilai2@huawei.com>
2024-03-08 17:26:00 +08:00
openharmony_ci b12567cc95 !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-Beta2 OpenHarmony-v4.0-Beta1 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:10:45 +00:00
fangting f06379f45c Add OAT.xml and README.OpenSource
Signed-off-by: fangting <fangting12@huawei.com>
2023-04-14 14:15:27 +08:00
openharmony_ci 4db4933862 !1 [syn]Add GN Build Files and Custom Modifications to Rust Third-party Libraries
Merge pull request !1 from lubinglun/master
2023-04-13 11:34:21 +00:00
lubinglun 414d017b95 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:27:08 +08:00
David Tolnay 35c51a44bb Release 1.0.107 github.com/dtolnay/syn/1.0.107 2022-12-18 08:56:42 -08:00
David Tolnay 9567370643 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 syn'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 08:49:21 -08:00
David Tolnay 04197dad82 Release 1.0.106 2022-12-17 12:03:30 -08:00
David Tolnay 938fd1dd1b Update build status badge 2022-12-17 12:02:54 -08:00
David Tolnay 5ebfe75e68 Merge pull request #1251 from dtolnay/instaloop
Fix invalid use of insta snapshot inside a loop
2022-12-03 13:28:05 -08:00
David Tolnay 8481196fb1 Fix invalid use of insta snapshot inside a loop 2022-12-03 13:16:17 -08:00
David Tolnay f991d68e9f Update test suite to nightly-2022-12-03 2022-12-02 18:51:37 -08:00
David Tolnay 05f69f7444 Release 1.0.105 2022-11-30 23:51:49 -08:00
David Tolnay 824935cab5 Merge pull request #1247 from dtolnay/punctdrop
Infer may_dangle on type parameters of Punctuated iterator Drop impls
2022-11-30 23:44:48 -08:00
David Tolnay 6b957bcbf6 Help infer may_dangle on type parameter of Punctuated iterator Drop impls 2022-11-30 23:30:51 -08:00
David Tolnay bd049f3833 Add regression test for issue 1246
error[E0505]: cannot move out of `p` because it is borrowed
      --> tests/test_iterators.rs:56:18
       |
    54 |     for element in &p {
       |                    --
       |                    |
       |                    borrow of `p` occurs here
       |                    a temporary with access to the borrow is created here ...
    55 |         if *element == 2 {
    56 |             drop(p);
       |                  ^ move out of `p` occurs here
    ...
    59 |     }
       |     - ... and the borrow might be used here, when that temporary is dropped and runs the destructor for type `syn::punctuated::Iter<'_, i32>`

    error[E0505]: cannot move out of `p` because it is borrowed
      --> tests/test_iterators.rs:64:18
       |
    62 |     for element in &mut p {
       |                    ------
       |                    |
       |                    borrow of `p` occurs here
       |                    a temporary with access to the borrow is created here ...
    63 |         if *element == 2 {
    64 |             drop(p);
       |                  ^ move out of `p` occurs here
    ...
    67 |     }
       |     - ... and the borrow might be used here, when that temporary is dropped and runs the destructor for type `syn::punctuated::IterMut<'_, i32>`
2022-11-30 22:37:38 -08:00
David Tolnay ad62ed6e1b Merge pull request #1245 from dtolnay/bounds
Improve dyn/impl-related parse errors
2022-11-30 22:11:53 -08:00
David Tolnay 11369719f3 Improve dyn/impl-related parse errors 2022-11-30 22:01:54 -08:00
David Tolnay a189cff9a1 Move TypeParamBound parse loop to associated function 2022-11-30 21:50:15 -08:00
David Tolnay 45b0a1dd74 Clean up naming in rustc syntax tree manipulation 2022-11-28 19:15:42 -08:00
David Tolnay f20c7ba346 Import token::Lit now there's no conflict with MetaItemLit 2022-11-28 19:11:45 -08:00
David Tolnay 3ded92a6ae Update test suite to nightly-2022-11-29 2022-11-28 19:10:13 -08:00
David Tolnay daf8dc05a9 Release 1.0.104 2022-11-27 17:42:18 -08:00
David Tolnay bf629a3517 Merge pull request #1244 from dtolnay/isnone
Make PathArguments::is_none() public
2022-11-27 17:41:41 -08:00
David Tolnay b5e92dfda4 Make PathArguments::is_none() public 2022-11-27 17:32:31 -08:00
David Tolnay 7d7c9ac3a1 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:19 -08:00
David Tolnay c2c44adf85 Update test suite to nightly-2022-11-25 2022-11-24 18:53:32 -08:00
David Tolnay 8d2da8d0db Update test suite to nightly-2022-11-24 2022-11-23 19:49:39 -08:00
David Tolnay 0e535dd256 Suppress "emit":"dep-info" json from syn-test-suite-feature-check
Previously:

    NOTE:  use --release
      Syn's test suite has some tests that run on every source file
      and test case in the rust-lang/rust repo, which can be pretty
      slow in debug mode. Consider running cargo test with `--release`
      to speed things up.
    {"artifact":"/git/syn/target/debug/deps/syn_test_suite-695bcafef2321389.d","emit":"dep-info"}
2022-11-22 22:47:28 -08:00
David Tolnay b6f106a089 Fix renamed let_underscore_drop lint
warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop`
       --> src/lib.rs:270:5
        |
    270 |     clippy::let_underscore_drop,
        |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop`
        |
        = note: `#[warn(renamed_and_removed_lints)]` on by default

    warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop`
      --> tests/crates/main.rs:13:10
       |
    13 | #![allow(clippy::let_underscore_drop)]
       |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop`
       |
       = note: `#[warn(renamed_and_removed_lints)]` on by default

    warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop`
     --> tests/features/macro/lib.rs:1:10
      |
    1 | #![allow(clippy::let_underscore_drop, clippy::toplevel_ref_arg)]
      |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop`
      |
      = note: `#[warn(renamed_and_removed_lints)]` on by default

    warning: lint `clippy::let_underscore_drop` has been renamed to `let_underscore_drop`
     --> tests/regression.rs:1:10
      |
    1 | #![allow(clippy::let_underscore_drop)]
      |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: use the new name: `let_underscore_drop`
      |
      = note: `#[warn(renamed_and_removed_lints)]` on by default
2022-11-22 22:38:08 -08:00
David Tolnay f791dc4c64 Update test suite to nightly-2022-11-23 2022-11-22 22:36:23 -08:00
David Tolnay 79ead8fbf7 Update test suite to nightly-2022-11-19 2022-11-18 22:11:00 -08:00
David Tolnay 413ab40eca Update test suite to nightly-2022-11-18 2022-11-17 23:10:59 -08:00
David Tolnay 43ff52ed15 Update test suite to nightly-2022-11-13 2022-11-12 21:32:46 -08:00
David Tolnay d525053d5d Ignore items_after_statements pedantic clippy lint
error: adding items after statements is confusing, since items exist from the start of the scope
       --> src/error.rs:139:9
        |
    139 | /         fn new(span: Span, message: String) -> Error {
    140 | |             Error {
    141 | |                 messages: vec![ErrorMessage {
    142 | |                     start_span: ThreadBound::new(span),
    ...   |
    146 | |             }
    147 | |         }
        | |_________^
        |
        = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#items_after_statements
        = note: `-D clippy::items-after-statements` implied by `-D clippy::pedantic`

    error: adding items after statements is confusing, since items exist from the start of the scope
       --> src/error.rs:167:9
        |
    167 | /         fn new_spanned(tokens: TokenStream, message: String) -> Error {
    168 | |             let mut iter = tokens.into_iter();
    169 | |             let start = iter.next().map_or_else(Span::call_site, |t| t.span());
    170 | |             let end = iter.last().map_or(start, |t| t.span());
    ...   |
    177 | |             }
    178 | |         }
        | |_________^
        |
        = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#items_after_statements

    error: adding items after statements is confusing, since items exist from the start of the scope
       --> src/error.rs:301:5
        |
    301 | /     fn new2(start: Span, end: Span, message: String) -> Error {
    302 | |         Error {
    303 | |             messages: vec![ErrorMessage {
    304 | |                 start_span: ThreadBound::new(start),
    ...   |
    308 | |         }
    309 | |     }
        | |_____^
        |
        = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#items_after_statements
2022-10-24 21:54:47 -07:00