pezkuwichain/pezkuwi-subxt
1
0
Fork 0
mirror of https://github.com/pezkuwichain/pezkuwi-subxt.git synced 2026-07-13 11:35:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove rustdocs allowances (#2797)

Browse Source 
Closes https://github.com/paritytech/polkadot-sdk-docs/issues/65
This commit is contained in:
Juan Girini
2023-12-24 09:03:37 +01:00
committed by GitHub
parent 8acd63003c
commit b4c816665b
8 changed files with 11 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sdk/src/polkadot_sdk/polkadot.rs
+3 -3
View File
@@ -50,7 +50,7 @@
//! correct execution of all parachain, without having all of its validators re-execute all
//! parachain blocks. When seen from this perspective, the fact that Polkadot executes different
//! parachains means it is a platform that has fully delivered (the holy grail of) "Full Execution
//! Sharding". TODO: link to approval checking article. https://github.com/paritytech/polkadot-sdk-docs/issues/66
//! Sharding". TODO: link to approval checking article. <https://github.com/paritytech/polkadot-sdk-docs/issues/66>
//! * A framework to build blockchains: In order to materialize the ecosystem of parachains, an easy
//! blockchain framework must exist. This is [Substrate](crate::polkadot_sdk::substrate),
//! [FRAME](crate::polkadot_sdk::frame_runtime) and [Cumulus](crate::polkadot_sdk::cumulus).
@@ -60,7 +60,7 @@
//!
//! > Note that the interoperability promised by Polkadot is unparalleled in that any two parachains
//! > connected to Polkadot have the same security and can have much better guarantees about the
//! > security of the recipient of any message. TODO: weakest link in bridges systems. https://github.com/paritytech/polkadot-sdk-docs/issues/66
//! > security of the recipient of any message. TODO: weakest link in bridges systems. <https://github.com/paritytech/polkadot-sdk-docs/issues/66>
//!
//! Polkadot delivers the above vision, alongside a flexible means for parachains to schedule
//! themselves with the Relay Chain. To achieve this, Polkadot has been developed with an
@@ -84,4 +84,4 @@
//! - RFC#5: [Coretime-interface](https://github.com/polkadot-fellows/RFCs/blob/main/text/0005-coretime-interface.md):
//! Interface for manipulating the usage of cores on the Polkadot Ubiquitous Computer.
// TODO: add more context and explanations about Polkadot as the Ubiquitous Computer and related
// tech. https://github.com/paritytech/polkadot-sdk-docs/issues/66
// tech. <https://github.com/paritytech/polkadot-sdk-docs/issues/66>
docs/sdk/src/polkadot_sdk/smart_contracts.rs
+2 -2
View File
@@ -1,9 +1,9 @@
//! # Smart Contracts
//!
//! TODO: @cmichi https://github.com/paritytech/polkadot-sdk-docs/issues/56
//! TODO: @cmichi <https://github.com/paritytech/polkadot-sdk-docs/issues/56>
//!
//! - WASM and EVM based, pallet-contracts and pallet-evm.
//! - single-daap-chain, transition from ink! to FRAME.
//! - Link to `use.ink`
//! - Link to [`crate::reference_docs::runtime_vs_smart_contract`].
//! - https://use.ink/migrate-ink-contracts-to-polkadot-frame-parachain/
//! - <https://use.ink/migrate-ink-contracts-to-polkadot-frame-parachain/>
docs/sdk/src/polkadot_sdk/substrate.rs
+1 -1
View File
@@ -143,7 +143,7 @@
//! - [`sc_consensus_aura`]
//! - [`sc_consensus_babe`]
//! - [`sc_consensus_grandpa`]
//! - [`sc_consensus_beefy`] (TODO: @adrian, add some high level docs https://github.com/paritytech/polkadot-sdk-docs/issues/57)
//! - [`sc_consensus_beefy`] (TODO: @adrian, add some high level docs <https://github.com/paritytech/polkadot-sdk-docs/issues/57>)
//! - [`sc_consensus_manual_seal`]
//! - [`sc_consensus_pow`]
docs/sdk/src/polkadot_sdk/xcm.rs
+1 -1
View File
@@ -2,4 +2,4 @@
//!
//! @KiChjang @franciscoaguirre
//! TODO: RFCs, xcm-spec, the future of the repo, minimal example perhaps, forward to where actual
//! docs are hosted. https://github.com/paritytech/polkadot-sdk-docs/issues/58
//! docs are hosted. <https://github.com/paritytech/polkadot-sdk-docs/issues/58>