Rust dilinde tip sisteminin (type system) sundu\u011fu en b\u00fcy\u00fck vaatlerden biri, bellek g\u00fcvenli\u011fi ile birlikte kodun \u00f6ng\u00f6r\u00fclebilir ve \u00e7ak\u0131\u015fmas\u0131z \u00e7al\u0131\u015fmas\u0131d\u0131r. Ancak harici k\u00fct\u00fcphaneler (crates) ile \u00e7al\u0131\u015f\u0131rken veya kendi veri tipleriniz i\u00e7in generic trait tan\u0131mlar\u0131 yazarken “E0117” veya “overlapping implementations” hatalar\u0131yla kar\u015f\u0131la\u015fabilirsiniz. Rust’\u0131n Orphan Rules (Yetim Kurallar\u0131) ve Coherence (Tutarl\u0131l\u0131k) mekanizmalar\u0131, projeniz b\u00fcy\u00fcd\u00fck\u00e7e kodun k\u0131r\u0131lamaz bir yap\u0131da kalmas\u0131n\u0131 garantiler.<\/p>\n
Bu makalede, Rust derleyicisinin tip \u00e7ak\u0131\u015fmalar\u0131n\u0131 nas\u0131l engelledi\u011fini, Blanket Implementations (Kapsaml\u0131 Uygulamalar) mant\u0131\u011f\u0131n\u0131 ve Covered Types (Kaplanm\u0131\u015f Tipler) istisnalar\u0131n\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz. B\u00f6ylece sistem mimarinizi kurarken derleyici ile sava\u015fmak yerine onun g\u00fcc\u00fcn\u00fc arkan\u0131za alacaks\u0131n\u0131z.<\/p>\n
Coherence (Tutarl\u0131l\u0131k), Rust tip sisteminin temel direklerinden biridir. Bu ilke basit bir kurala dayan\u0131r: Belirli bir tip i\u00e7in, belirli bir Trait (Aray\u00fcz) tan\u0131m\u0131n\u0131n sistem genelinde yaln\u0131zca tek bir uygulamas\u0131 (implementation)<\/strong> olabilir. Aksi takdirde, derleyici hangi kod blo\u011funu \u00e7a\u011f\u0131raca\u011f\u0131n\u0131 bilemez ve belirsizlik (ambiguity) ortaya \u00e7\u0131kar.<\/p>\n \u00d6rne\u011fin, C++ dilinde “One Definition Rule” (ODR) ihlalleri s\u0131kl\u0131kla \u00e7al\u0131\u015fma zaman\u0131 (runtime) hatalar\u0131na veya beklenmeyen davran\u0131\u015flara yol a\u00e7ar. Rust ise bu sorunu derleme zaman\u0131nda (compile-time) \u00e7\u00f6zer. E\u011fer iki farkl\u0131 k\u00fct\u00fcphane ayn\u0131 tip i\u00e7in ayn\u0131 davran\u0131\u015f\u0131 farkl\u0131 \u015fekillerde tan\u0131mlayabilseydi, uygulaman\u0131z ba\u011f\u0131ml\u0131l\u0131klar\u0131 g\u00fcncelledi\u011finde \u00e7\u00f6kerdi.<\/p>\n Coherence ilkesini korumak i\u00e7in Rust derleyicisi iki ana kural grubuna dayan\u0131r:<\/p>\n Bu ilkeler sayesinde, yazd\u0131\u011f\u0131n\u0131z bir Rust kodu ba\u015fka bir k\u00fct\u00fcphane g\u00fcncellendi\u011finde sessizce bozulmaz. Derleyici, gelecekte olu\u015fabilecek olas\u0131 \u00e7ak\u0131\u015fmalar\u0131 (overlapping) \u00f6nceden sezer ve derlemeyi durdurur.<\/p>\n Orphan Rules (Yetim Kurallar\u0131), ismini romantik bir benzetmeden al\u0131r: E\u011fer ne Trait ne de Tip sizin projenize (crate) ait de\u011filse, bu uygulama “yetim” kal\u0131r ve derleyici taraf\u0131ndan reddedilir. Yani bir Bu kural\u0131n ge\u00e7erli oldu\u011fu ve olmad\u0131\u011f\u0131 durumlar\u0131 a\u015fa\u011f\u0131daki kod \u00f6rne\u011fiyle inceleyelim:<\/p>\n E\u011fer DURUM 3’e izin verilseydi ve projenize ekledi\u011finiz ba\u015fka bir k\u00fct\u00fcphane de Bazen harici bir veri tipine (\u00f6rne\u011fin Newtype kal\u0131b\u0131, harici tipi tek elemanl\u0131 bir Tuple Struct i\u00e7ine sarmallayarak yerel (local) bir tip olu\u015fturma i\u015flemidir:<\/p>\n Nitekim bu yakla\u015f\u0131m, s\u0131f\u0131r maliyetli soyutlama (zero-cost abstraction) sa\u011flar. Derleme a\u015famas\u0131ndan sonra wrapping (sarmallama) katman\u0131 optimize edilir ve bellekte fazladan y\u00fck olu\u015fturmaz.<\/p>\n Blanket Implementations, belirli \u015fartlar\u0131 sa\u011flayan t\u00fcm<\/em> tipler i\u00e7in ge\u00e7erli olan genel trait uygulamalar\u0131d\u0131r. Rust standart k\u00fct\u00fcphanesinde bu desen son derece yayg\u0131nd\u0131r. \u00d6rne\u011fin, Standart k\u00fct\u00fcphanedeki Blanket Implementation \u00f6rne\u011fi \u015fu \u015fekildedir:<\/p>\n Blanket implementations g\u00fc\u00e7l\u00fc bir soyutlama arac\u0131d\u0131r; fakat k\u00fct\u00fcphane geli\u015ftiricileri i\u00e7in ciddi sorumluluklar getirir. \u00c7\u00fcnk\u00fc bir kez blanket impl tan\u0131mlad\u0131\u011f\u0131n\u0131zda, gelecekte kullan\u0131c\u0131lar\u0131n yazabilece\u011fi \u00f6zel Kendi k\u00fct\u00fcphanenizde geni\u015f kapsaml\u0131 bir blanket impl tan\u0131mlarken \u00e7ok dikkatli olmal\u0131s\u0131n\u0131z. \u00d6rne\u011fin, kendi yazd\u0131\u011f\u0131n\u0131z bir k\u00fct\u00fcphanede generic her tip i\u00e7in bir trait uygulamaya \u00e7al\u0131\u015fal\u0131m:<\/p>\n Bu kodu yazd\u0131\u011f\u0131n\u0131z anda, sistemdeki istisnas\u0131z t\u00fcm tipler<\/strong> (i32, String, sizin struct’lar\u0131n\u0131z, harici struct’lar) bu trait’i uygulam\u0131\u015f olur. Dolay\u0131s\u0131yla, projenizin ba\u015fka bir yerinde belirli bir tip i\u00e7in \u00f6zel bir Rust RFC 2451 ile birlikte Orphan Rules esnetilmi\u015f ve daha mant\u0131kl\u0131 bir esnekli\u011fe kavu\u015fturulmu\u015ftur. Bu g\u00fcncelleme, generic parametrelerin trait uygulamas\u0131nda nas\u0131l yer ald\u0131\u011f\u0131na ba\u011fl\u0131 olarak kural\u0131 yumu\u015fat\u0131r. \u0130\u015fte bu noktada Covered Types (Kaplanm\u0131\u015f Tipler)<\/strong> kavram\u0131 devreye girer.<\/p>\n Bir generic tip parametresi (\u00f6rne\u011fin Derleyicinin kurallar\u0131n\u0131 anlamak i\u00e7in a\u015fa\u011f\u0131daki tabloyu inceleyelim:<\/p>\n Bu kurallar sayesinde, k\u00fct\u00fcphanelerin generic tipleri daha g\u00fcvenli bir \u015fekilde sarmalamas\u0131 ve geni\u015fletmesi m\u00fcmk\u00fcn k\u0131l\u0131nm\u0131\u015ft\u0131r. Bazen karma\u015f\u0131k g\u00f6r\u00fcnse de temeldeki ama\u00e7, iki farkl\u0131 k\u00fct\u00fcphanenin ayn\u0131 generic tipe m\u00fcdahale ederek \u00e7ak\u0131\u015fma yaratmas\u0131n\u0131 matematiksel olarak imkans\u0131z k\u0131lmakt\u0131r.<\/p>\n Konuyu somutla\u015ft\u0131rmak ad\u0131na, T\u00fcrkiye’de bir e-ticaret altyap\u0131s\u0131 geli\u015ftirdi\u011finizi varsayal\u0131m. Sisteminizde harici bir SQL s\u00fcr\u00fcc\u00fcs\u00fc (\u00f6rne\u011fin Kar\u015f\u0131la\u015fabilece\u011finiz senaryoyu ad\u0131m ad\u0131m inceleyelim.<\/p>\n \u00d6ncelikle do\u011frudan harici tipleri ba\u011flamaya \u00e7al\u0131\u015fal\u0131m:<\/p>\n Bu sorunu \u00e7\u00f6zmek i\u00e7in mimarimize yerel bir sarmalay\u0131c\u0131 (wrapper) veya yerel bir domain modeli eklemeliyiz. \u0130deal \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131 \u015fu \u015fekildedir:<\/p>\n Nitekim bu mimari yakla\u015f\u0131m sayesinde hem k\u00fct\u00fcphanelerin ba\u011f\u0131ml\u0131l\u0131klar\u0131ndan korunduk hem de Rust derleyicisinin tutarl\u0131l\u0131k (coherence) kurallar\u0131n\u0131 ihlal etmeden kodumuzu derleyebildik.<\/p>\n Rust derleyicisi bir \u00d6zellikle ikinci soru hayati \u00f6nem ta\u015f\u0131r. Rust tasar\u0131mc\u0131lar\u0131 “Future Compatibility” (Gelece\u011fe Uyumluluk) ilkesine b\u00fcy\u00fck de\u011fer verir. E\u011fer bug\u00fcn yazd\u0131\u011f\u0131n\u0131z kod, ba\u011f\u0131ml\u0131 oldu\u011funuz bir k\u00fct\u00fcphane yar\u0131n yeni bir \u00d6rnek bir \u00e7ak\u0131\u015fma durumuna bakal\u0131m:<\/p>\n Derleyici, iki farkl\u0131 generic k\u0131s\u0131t\u0131n (trait bound) tek bir tip \u00fczerinde \u00e7ak\u0131\u015fma ihtimalini sezer sezmez derlemeyi engeller. Dolay\u0131s\u0131yla \u00e7ak\u0131\u015fmay\u0131 \u00f6nlemek i\u00e7in her zaman spesifik tiplere odaklanmal\u0131 veya trait’leri daha dar kapsama almal\u0131s\u0131n\u0131z.<\/p>\n Rust’\u0131n tip kontrol mekanizmas\u0131 s\u00fcrekli geli\u015fmektedir. Mevcut derleyici mant\u0131\u011f\u0131 zaman zaman geli\u015ftiricilere \u00e7ok kat\u0131 gelebilir. Bu k\u0131s\u0131tlamalar\u0131 daha zeki bir mant\u0131k motoruna oturtmak amac\u0131yla Rust ekibi Chalk<\/strong> ad\u0131 verilen yeni bir trait \u00e7\u00f6z\u00fcc\u00fc (trait solver) \u00fczerinde \u00e7al\u0131\u015fmaktad\u0131r.<\/p>\n Chalk, Prolog benzeri mant\u0131ksal programlama kurallar\u0131 kullanarak trait ili\u015fkilerini birer matematiksel denklem gibi \u00e7\u00f6zer. Chalk motoru tamamen entegre edildi\u011finde:<\/p>\n A\u015fa\u011f\u0131daki g\u00f6rsel s\u00fcre\u00e7 \u015femas\u0131, derleyicinin bir [Yerel Trait mi?] \u2500\u2500(Evet)\u2500\u2500> [GE\u00c7ERL\u0130] Hay\u0131r, kesinlikle yol a\u00e7maz. Rust’ta Newtype pattern genellikle tek elemanl\u0131 tuple struct’lar \u00fczerinden kurulur. Derleme a\u015famas\u0131nda derleyici bu sarmalay\u0131c\u0131y\u0131 tamamen ortadan kald\u0131r\u0131r (zero-cost abstraction). Bellek d\u00fczeni (memory layout) sarmalanan tip ile birebir ayn\u0131 kal\u0131r. Ekstra bir g\u00fcvenlik ve netlik istiyorsan\u0131z struct \u00fczerine \u0130lk olarak uygulayamad\u0131\u011f\u0131n\u0131z Trait veya Tipin hangisinin size (mevcut crate’e) ait olmad\u0131\u011f\u0131n\u0131 tespit edin. E\u011fer ikisi de harici bir k\u00fct\u00fcphaneye aitse, harici tipi yerel bir struct i\u00e7ine sarmallamak (Newtype deseni) en h\u0131zl\u0131 \u00e7\u00f6z\u00fcmd\u00fcr. Alternatif olarak, e\u011fer mimariniz elveriyorsa kendi trait’inizi yaz\u0131p harici tipe bu trait’i uygulayabilirsiniz.<\/p>\n Blanket implementation yazarken trait bounds (trait s\u0131n\u0131rlar\u0131) ifadelerinizi olabildi\u011fince dar tutun. Sadece generic parametrelerden en az biri sizin yerel bir tipiniz taraf\u0131ndan kaplanm\u0131\u015fsa (covered type) uygulanabilir. \u00d6rne\u011fin #RustLang #Yaz\u0131l\u0131mGeli\u015ftirme #SistemProgramlama #RustT\u00fcrkiye #WebGeli\u015ftirme<\/p>\n\n
Type<\/code> ve Trait<\/code> \u00e7ifti i\u00e7in asla birden fazla impl<\/code> blo\u011fu bulunamaz.<\/li>\nOrphan Rules (Yetim Kurallar\u0131) Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/h2>\n
impl<\/code> blo\u011fu yazabilmeniz i\u00e7in \u015fu iki ko\u015fuldan en az birinin<\/strong> yerel (local) olmas\u0131 gerekir:<\/p>\n\n
Trait<\/code> sizin crate’inizde tan\u0131mlanm\u0131\u015f olmal\u0131d\u0131r.<\/li>\nType<\/code> (Hedef Tip) sizin crate’inizde tan\u0131mlanm\u0131\u015f olmal\u0131d\u0131r.<\/li>\n<\/ol>\nuse std::fmt::Display;\n\n\/\/ DURUM 1: GE\u00c7ERL\u0130 (Tip bize ait)\npub struct Kullanici {\n pub isim: String,\n}\n\nimpl Display for Kullanici {\n fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {\n write!(f, \"Kullan\u0131c\u0131: {}\", self.isim)\n }\n}\n\n\/\/ DURUM 2: GE\u00c7ERL\u0130 (Trait bize ait)\npub trait Yazdirilabilir {\n fn detay_goster(&self);\n}\n\nimpl Yazdirilabilir for String {\n fn detay_goster(&self) {\n println!(\"Metin i\u00e7eri\u011fi: {}\", self);\n }\n}\n\n\/\/ DURUM 3: GE\u00c7ERS\u0130Z - E0117 Hatas\u0131 (Ne trait ne tip bize ait!)\n\/\/ impl Display for Vec<u8> { ... }\n<\/code><\/pre>\n<\/div>\nVec<u8><\/code> i\u00e7in Display<\/code> uygulasa\u0131yd\u0131, derleyici hangi uygulamay\u0131 se\u00e7ece\u011fini bilemezdi. Bu k\u0131s\u0131tlama, yaz\u0131l\u0131m ekosisteminin kararl\u0131l\u0131\u011f\u0131 i\u00e7in kritik bir g\u00fcvencedir.<\/p>\nOrphan Rules Engelini A\u015fmak: Newtype Kal\u0131b\u0131 (Design Pattern)<\/h3>\n
std::vec::Vec<\/code>) harici bir trait (\u00f6rne\u011fin serde::Serialize<\/code>) uygulaman\u0131z gerekebilir. Orphan rules nedeniyle bunu do\u011frudan yapamazs\u0131n\u0131z. Bu durumda Rust toplulu\u011funun standart \u00e7\u00f6z\u00fcm\u00fc Newtype Kal\u0131b\u0131<\/strong> kullanmakt\u0131r.<\/p>\nuse std::fmt;\n\n\/\/ Harici Vec<String> tipini yerel bir struct ile sarmall\u0131yoruz\npub struct EtiketListesi(pub Vec<String>);\n\n\/\/ Art\u0131k 'EtiketListesi' bizim tipimiz oldu\u011fu i\u00e7in harici 'Display' trait'ini uygulayabiliriz!\nimpl fmt::Display for EtiketListesi {\n fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {\n write!(f, \"Etiketler: {}\", self.0.join(\", \"))\n }\n}\n<\/code><\/pre>\n<\/div>\nBlanket Implementations (Kapsaml\u0131 Uygulamalar) Nedir?<\/h2>\n
Display<\/code> trait’ini uygulayan her tip otomatik olarak ToString<\/code> trait’ine de sahip olur.<\/p>\n\/\/ Display yetene\u011fi olan HERHANG\u0130 bir T tipi i\u00e7in ToString trait'ini uygula\nimpl<T: fmt::Display> ToString for T {\n fn to_string(&self) -> String {\n \/\/ ...\n }\n}\n<\/code><\/pre>\n<\/div>\nimpl<\/code> bloklar\u0131n\u0131 k\u0131s\u0131tlam\u0131\u015f olursunuz.<\/p>\nGeneric Tipler \u00dczerinde Blanket Impl Yazman\u0131n Tehlikeleri<\/h3>\n
pub trait D\u00f6n\u00fc\u015ft\u00fcr\u00fcc\u00fc {\n fn d\u00f6n\u00fc\u015ft\u00fcr(&self) -> String;\n}\n\n\/\/ TEHL\u0130KEL\u0130: T\u00fcm T tipleri i\u00e7in bu trait'i uyguluyoruz!\nimpl<T> D\u00f6n\u00fc\u015ft\u00fcr\u00fcc\u00fc for T {\n fn d\u00f6n\u00fc\u015ft\u00fcr(&self) -> String {\n String::from(\"Genel d\u00f6n\u00fc\u015f\u00fcm\")\n }\n}\n<\/code><\/pre>\n<\/div>\nD\u00f6n\u00fc\u015ft\u00fcr\u00fcc\u00fc<\/code> mant\u0131\u011f\u0131 yazmak istedi\u011finizde Rust derleyicisi “conflicting implementations” (\u00e7ak\u0131\u015fan uygulamalar) hatas\u0131 verecektir.<\/p>\nCovered Types (Kaplanm\u0131\u015f Tipler) ve Orphan Rules \u0130stisnalar\u0131<\/h2>\n
T<\/code>), yerel bir tipin (\u00f6rne\u011fin MyStruct<T><\/code>) i\u00e7inde yer al\u0131yorsa, bu T<\/code> parametresine “Covered” (Kaplanm\u0131\u015f) denir. E\u011fer generic parametre do\u011frudan veya sadece harici bir tipin i\u00e7inde (\u00f6rne\u011fin Vec<T><\/code>) bulunuyorsa, buna “Uncovered” denir.<\/p>\n\n\n
\n \nKod Yap\u0131s\u0131 (Implementation)<\/th>\n Durum<\/th>\n A\u00e7\u0131klama<\/th>\n<\/tr>\n<\/thead>\n \n impl<T> HariciTrait for MyType<T><\/code><\/td>\nGe\u00e7erli<\/td>\n Ana hedef tip ( MyType<\/code>) yereldir.<\/td>\n<\/tr>\n\n impl<T> HariciTrait<MyType> for T<\/code><\/td>\nGe\u00e7erli<\/td>\n Harici Trait, yerel bir tipi generic olarak kapsar.<\/td>\n<\/tr>\n \n impl<T> HariciTrait<T> for Vec<T><\/code><\/td>\nGe\u00e7ersiz<\/td>\n Vec<\/code> haricidir ve T<\/code> kaplanmam\u0131\u015ft\u0131r (Uncovered).<\/td>\n<\/tr>\n\n impl<T> HariciTrait<MyType<T>> for Vec<T><\/code><\/td>\nGe\u00e7erli<\/td>\n T<\/code> parametresi yerel MyType<\/code> i\u00e7inde kaplanm\u0131\u015ft\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nGer\u00e7ek D\u00fcnya Senaryosu: Serde ve Veritaban\u0131 S\u00fcr\u00fcc\u00fcs\u00fc Entegrasyonu<\/h2>\n
sqlx<\/code>) ve harici bir serile\u015ftirme k\u00fct\u00fcphanesi (\u00f6rne\u011fin serde<\/code>) kullan\u0131yorsunuz. Veritaban\u0131ndan gelen karma\u015f\u0131k JSON verilerini kendi veri modelinize d\u00f6n\u00fc\u015ft\u00fcrmek istiyorsunuz.<\/p>\nSorunun Ortaya \u00c7\u0131kmas\u0131<\/h3>\n
\/\/ Projenizdeki main.rs veya lib.rs\nuse serde::Serialize;\nuse sqlx::types::Json; \/\/ Harici crate'den gelen tip\n\n\/\/ HATA! Hem Serialize trait'i hem de Json struct'\u0131 harici crate'lere ait!\n\/\/ Compiler Error: E0117\n\/*\nimpl<T> Serialize for Json<T> {\n fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>\n where\n S: serde::Serializer,\n {\n \/\/ ...\n }\n}\n*\/\n<\/code><\/pre>\n<\/div>\n\u00c7\u00f6z\u00fcm: Covered Type ve Newtype Pattern Mimarisi<\/h3>\n
use serde::{Serialize, Serializer};\nuse sqlx::types::Json as SqlxJson;\n\n\/\/ Ad\u0131m 1: Kendi projemize ait (Local) bir Newtype tan\u0131ml\u0131yoruz\npub struct VeritabaniJson<T>(pub SqlxJson<T>);\n\n\/\/ Ad\u0131m 2: Art\u0131k VeritabaniJson bizim tipimiz oldu\u011fu i\u00e7in \n\/\/ harici Serialize trait'ini sorunsuzca uygulayabiliriz!\nimpl<T: Serialize> Serialize for VeritabaniJson<T> {\n fn serialize<S>(&self, serializer: S) -> Result<S::Ok, S::Error>\n where\n S: Serializer,\n {\n \/\/ Sarmalanan i\u00e7 tipe ula\u015f\u0131p serile\u015ftiriyoruz\n self.0.0.serialize(serializer)\n }\n}\n\n\/\/ Ad\u0131m 3: Kullan\u0131m Alan\u0131\n#[derive(Serialize)]\npub struct SiparisDetay {\n pub urun_adi: String,\n pub fiyat: f64,\n}\n\npub fn siparis_isle() {\n let veri = SiparisDetay {\n urun_adi: String::from(\"Kablosuz Klavye\"),\n fiyat: 1250.50,\n };\n \n let sqlx_json = SqlxJson(veri);\n let yerel_json = VeritabaniJson(sqlx_json);\n \n \/\/ Derleyiciye tak\u0131lmadan g\u00fcvenle serile\u015ftirme yapabiliyoruz\n let json_cikti = serde_json::to_string(&yerel_json).unwrap();\n println!(\"{}\", json_cikti);\n}\n<\/code><\/pre>\n<\/div>\nRust Derleyicisi \u00c7ak\u0131\u015fmalar\u0131 (Overlapping Impls) Nas\u0131l Engeller?<\/h2>\n
impl<\/code> blo\u011fu g\u00f6rd\u00fc\u011f\u00fcnde, negatif hipotezler (negative reasoning) ve pozitif mant\u0131k kurallar\u0131 ile \u00e7\u0131kar\u0131m yapar. \u0130ki farkl\u0131 impl<\/code> blo\u011funun birbiriyle \u00f6rt\u00fc\u015f\u00fcp \u00f6rt\u00fc\u015fmedi\u011fini belirlemek i\u00e7in derleyici \u015fu sorular\u0131 sorar:<\/p>\n\n
impl<\/code> ekledi\u011finde bozulacaksa, Rust derleyicisi bug\u00fcn yaz\u0131lan kodu reddeder.<\/p>\npub trait Sifreleyici {\n fn sifrele(&self) -> String;\n}\n\n\/\/ Blok 1: AsRef<str> olan her tip i\u00e7in\nimpl<T: AsRef<str>> Sifreleyici for T {\n fn sifrele(&self) -> String {\n format!(\"STR Sifre: {}\", self.as_ref())\n }\n}\n\n\/\/ Blok 2: AsMut<[u8]> olan her tip i\u00e7in\n\/\/ HATA: Hem AsRef<str> hem de AsMut<[u8]> uygulayan bir T tipi var olabilir! (\u00d6rn: Vec<u8> veya \u00f6zel tipler)\n\/*\nimpl<T: AsMut<[u8]>> Sifreleyici for T {\n fn sifrele(&self) -> String {\n String::from(\"Byte Sifre\")\n }\n}\n*\/\n<\/code><\/pre>\n<\/div>\nGelece\u011fin Rust’\u0131: Coherence \u0130yile\u015ftirmeleri ve Chalk Projesi<\/h2>\n
\n
impl !Trait for Type<\/code>) mant\u0131\u011f\u0131 daha kararl\u0131 \u00e7al\u0131\u015farak, “bu tip bu trait’i ASLA uygulamayacak” garantisi \u00fczerinden yeni blanket impl imkanlar\u0131 do\u011furacakt\u0131r.<\/li>\nimpl<\/code> blo\u011funu kontrol ederken ge\u00e7ti\u011fi a\u015famalar\u0131 \u00f6zetlemektedir:<\/p>\n
\n \u2502
\n (Hay\u0131r)
\n \u25bc
\n[Yerel Tip mi?] \u2500\u2500(Evet)\u2500\u2500> [GE\u00c7ERL\u0130]
\n \u2502
\n (Hay\u0131r)
\n \u25bc
\n[Generic Parametre Kaplanm\u0131\u015f m\u0131? (Covered Type)] \u2500\u2500(Evet)\u2500\u2500> [GE\u00c7ERL\u0130]
\n \u2502
\n (Hay\u0131r)
\n \u25bc
\n[REDDED\u0130LD\u0130: E0117 Orphan Rule \u0130hlali]<\/p>\nS\u0131k\u00e7a Sorulan Sorular (SSS)<\/h2>\n
1. Newtype pattern kullan\u0131m\u0131 performans kayb\u0131na (overhead) yol a\u00e7ar m\u0131?<\/h3>\n
#[repr(transparent)]<\/code> \u00f6zniteli\u011fini ekleyebilirsiniz.<\/p>\n2. E0117 hatas\u0131 ald\u0131\u011f\u0131mda atmam gereken ilk ad\u0131m nedir?<\/h3>\n
3. Blanket Implementation yazarken \u00e7ak\u0131\u015fmalar\u0131 engellemek i\u00e7in ne yapmal\u0131y\u0131m?<\/h3>\n
impl<T> MyTrait for T<\/code> \u015feklinde t\u00fcm tipleri hedefleyen blanket impl’ler, k\u00fct\u00fcphanenizin esnekli\u011fini k\u0131s\u0131tlar. Bunun yerine impl<T: MySpecificMarker> MyTrait for T<\/code> gibi i\u015faret\u00e7i (marker) trait’lerle hedefinizi daralt\u0131n.<\/p>\n4. Foreign Trait harici bir generic tipe uygulanabilir mi?<\/h3>\n
impl<T> ForeignTrait<MyLocalType> for ForeignType<T><\/code> ifadesi ge\u00e7erlidir; fakat impl<T> ForeignTrait<T> for ForeignType<T><\/code> ifadesi orphan kurallar\u0131n\u0131 ihlal eder.<\/p>\n