Skip to content

Commit e73eff8

Browse files
committed
fix: update meta tags and remove redundant content
- Updated og:description and twitter:description meta tags to reflect the blog's content - Removed redundant 'About' section content from the index page
1 parent 5ac02a3 commit e73eff8

File tree

2 files changed

+4
-7
lines changed

2 files changed

+4
-7
lines changed

index.html

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,15 +8,15 @@
88
<title>DEV×PAIN</title><meta name="Description" content="DEV×Pain&#39;s Blog on Tech, Trading, and Rust 🦀"><meta property="og:url" content="https://pain.devxfamily.com/">
99
<meta property="og:site_name" content="DEV×PAIN">
1010
<meta property="og:title" content="Home">
11-
<meta property="og:description" content="Ex-game dev transitioning into web, crypto, and algo trading. Building with Rust 🦀, sharing my journey, growing a community, and actively seeking roles in tech">
11+
<meta property="og:description" content="DEV×Pain&#39;s Blog on Tech, Trading, and Rust 🦀">
1212
<meta property="og:locale" content="en">
1313
<meta property="og:type" content="website">
1414
<meta property="og:image" content="https://pain.devxfamily.com/logo.png">
1515

1616
<meta name="twitter:card" content="summary_large_image">
1717
<meta name="twitter:image" content="https://pain.devxfamily.com/logo.png">
1818
<meta name="twitter:title" content="Home">
19-
<meta name="twitter:description" content="Ex-game dev transitioning into web, crypto, and algo trading. Building with Rust 🦀, sharing my journey, growing a community, and actively seeking roles in tech">
19+
<meta name="twitter:description" content="DEV×Pain&#39;s Blog on Tech, Trading, and Rust 🦀">
2020
<meta name="twitter:site" content="@devxpain0">
2121
<meta name="application-name" content="DEV×PAIN">
2222
<meta name="apple-mobile-web-app-title" content="DEV×PAIN"><meta name="theme-color" content="#ffffff"><meta name="msapplication-TileColor" content="#da532c"><link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" />
@@ -99,10 +99,7 @@
9999
data-sizes="auto"
100100
alt="/images/pain.png"
101101
title="/images/pain.png" width="1024" height="1024" /></a></div><div class="home-subtitle"><div id="id-1" class="typeit"></div></div><div class="links"><a href="https://github.com/devxpain" title="GitHub" target="_blank" rel="noopener noreffer me"><i class="fab fa-github fa-fw" aria-hidden="true"></i></a><a href="https://twitter.com/devxpain0" title="Twitter" target="_blank" rel="noopener noreffer me"><i class="fab fa-twitter fa-fw" aria-hidden="true"></i></a><a href="https://www.youtube.com/@devxpain" title="YouTube" target="_blank" rel="noopener noreffer me"><i class="fab fa-youtube fa-fw" aria-hidden="true"></i></a><a href="https://www.twitch.tv/devxpain" title="Twitch" target="_blank" rel="noopener noreffer me"><i class="fab fa-twitch fa-fw" aria-hidden="true"></i></a><a href="/index.xml" title="RSS" target="_blank" rel="noopener noreffer me"><i class="fas fa-rss fa-fw" aria-hidden="true"></i></a></div></div>
102-
<div class="single">
103-
<div class="content" id="content"><p>Ex-game dev transitioning into web, crypto, and algo trading. Building with Rust 🦀, sharing my journey, growing a community, and actively seeking roles in tech</p>
104-
</div>
105-
</div><article class="single summary" itemscope itemtype="http://schema.org/Article"><h1 class="single-title" itemprop="name headline">
102+
<article class="single summary" itemscope itemtype="http://schema.org/Article"><h1 class="single-title" itemprop="name headline">
106103
<a href="/how-to-check-traits-implemented-for-a-struct-or-enum/">Rust Tips: How to Check Traits Implemented for a Struct or Enum</a>
107104
</h1><div class="post-meta"><span class="post-author"><a href="https://pain.devxfamily.com" title="Author" target="_blank" rel="noopener noreffer author" class="author"><i class="fas fa-user-circle fa-fw" aria-hidden="true"></i>devxpain</a></span>&nbsp;<span class="post-publish">published on <time datetime="2025-01-04">2025-01-04</time></span>&nbsp;<span class="post-category">included in <a href="/categories/rust/"><i class="far fa-folder fa-fw" aria-hidden="true"></i>Rust</a></span></div><div class="content"><p>When transitioning from OOP languages to Rust, you might notice some differences in how traits (similar to interface in Java) are handled. In OOP, a class often centralizes information about inherited interfaces, making it easy to see at a glance.</p>
108105
<h2 id="java-example">Java Example</h2>

index.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
[{"categories":null,"content":"Ex-game dev transitioning into web, crypto, and algo trading. Building with Rust 🦀, sharing my journey, growing a community, and actively seeking roles in tech ","date":"2025-01-05","objectID":"/about/:0:0","tags":null,"title":"About","uri":"/about/"},{"categories":["rust"],"content":"When transitioning from OOP languages to Rust, you might notice some differences in how traits (similar to interface in Java) are handled. In OOP, a class often centralizes information about inherited interfaces, making it easy to see at a glance. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:0:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Java Example // Interfaces.java interface InterfaceA { void methodA(); } interface InterfaceB { void methodB(); } // ConcreteClass.java public class ConcreteClass implements InterfaceA, InterfaceB { @Override public void methodA() { // Implementation for methodA } @Override public void methodB() { // Implementation for methodB } } In Rust, however, traits implemented by a struct or enum might not be as immediately obvious, since their implementations can be scattered across multiple files. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:1:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Rust Example // interfaces.rs pub trait InterfaceA { fn method_a(\u0026self); } pub trait InterfaceB { fn method_b(\u0026self); } // concrete_struct.rs pub struct ConcreteStruct; impl ConcreteStruct { pub fn new() -\u003e Self { ConcreteStruct } } // impl_a.rs use crate::interfaces::InterfaceA; use crate::concrete_struct::ConcreteStruct; impl InterfaceA for ConcreteStruct { fn method_a(\u0026self) { // Implementation for method_a } } // impl_b.rs use crate::interfaces::InterfaceB; use crate::concrete_struct::ConcreteStruct; impl InterfaceB for ConcreteStruct { fn method_b(\u0026self) { // Implementation for method_b } } Thankfully, rust-analyzer, a powerful tool for Rust developers, bridges this gap and makes exploring trait implementations seamless. In this article, we’ll explore how to leverage rust-analyzer in NeoVim and VSCode to quickly check which traits a Rust struct or enum implements. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:2:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"NeoVim: Leveraging rustaceanvim [^1] If you’re using NeoVim, here’s how you can easily inspect trait implementations: Set Up rustaceanvim: Ensure you have rustaceanvim configured as your Rust development environment. Navigate to the Symbol: Place your cursor over the struct or enum whose trait implementations you want to inspect. Open the Symbol Inspector: Press SHIFT+K twice. This opens the symbol inspector, displaying useful information about the symbol. Find Trait Implementations: Look for the line that says “Go to [x] implementations” (where x represents the number of implementations). Press Enter to open a window showing all the traits implemented by that symbol. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:3:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"VSCode: Simplified with rust-analyzer VSCode users can also take advantage of rust-analyzer for similar functionality. Here’s how: Install rust-analyzer Extension: Make sure you have the rust-analyzer extension installed and enabled in your VSCode setup. Navigate to the Symbol: Click or place your cursor on the struct or enum you’re interested in. Open the Symbol Inspector: Press SHIFT+K once. This opens a detailed view of the symbol, including trait implementations. Explore Implementations: Click on the “[x] implementations” link. A new window will appear, listing all the traits implemented by the symbol. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:4:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Why This Matters Understanding which traits a struct or enum implements is essential for maintaining and debugging Rust code, especially in larger projects. By integrating rust-analyzer into your workflow, you can overcome Rust’s decentralized trait implementation syntax and make your development process smoother. Whether you’re using NeoVim or VSCode, rust-analyzer empowers you to navigate and understand your codebase with confidence. Try these tips today and experience the productivity boost firsthand! ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:5:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"References [^1] rustaceanvim ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:6:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"}]
1+
[{"categories":null,"content":"Ex-game dev transitioning into web, crypto, and algo trading. Building with Rust 🦀, sharing my journey, growing a community, and actively seeking roles in tech ","date":"2025-01-05","objectID":"/about/:0:0","tags":[],"title":"About","uri":"/about/"},{"categories":["rust"],"content":"When transitioning from OOP languages to Rust, you might notice some differences in how traits (similar to interface in Java) are handled. In OOP, a class often centralizes information about inherited interfaces, making it easy to see at a glance. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:0:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Java Example // Interfaces.java interface InterfaceA { void methodA(); } interface InterfaceB { void methodB(); } // ConcreteClass.java public class ConcreteClass implements InterfaceA, InterfaceB { @Override public void methodA() { // Implementation for methodA } @Override public void methodB() { // Implementation for methodB } } In Rust, however, traits implemented by a struct or enum might not be as immediately obvious, since their implementations can be scattered across multiple files. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:1:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Rust Example // interfaces.rs pub trait InterfaceA { fn method_a(\u0026self); } pub trait InterfaceB { fn method_b(\u0026self); } // concrete_struct.rs pub struct ConcreteStruct; impl ConcreteStruct { pub fn new() -\u003e Self { ConcreteStruct } } // impl_a.rs use crate::interfaces::InterfaceA; use crate::concrete_struct::ConcreteStruct; impl InterfaceA for ConcreteStruct { fn method_a(\u0026self) { // Implementation for method_a } } // impl_b.rs use crate::interfaces::InterfaceB; use crate::concrete_struct::ConcreteStruct; impl InterfaceB for ConcreteStruct { fn method_b(\u0026self) { // Implementation for method_b } } Thankfully, rust-analyzer, a powerful tool for Rust developers, bridges this gap and makes exploring trait implementations seamless. In this article, we’ll explore how to leverage rust-analyzer in NeoVim and VSCode to quickly check which traits a Rust struct or enum implements. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:2:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"NeoVim: Leveraging rustaceanvim [^1] If you’re using NeoVim, here’s how you can easily inspect trait implementations: Set Up rustaceanvim: Ensure you have rustaceanvim configured as your Rust development environment. Navigate to the Symbol: Place your cursor over the struct or enum whose trait implementations you want to inspect. Open the Symbol Inspector: Press SHIFT+K twice. This opens the symbol inspector, displaying useful information about the symbol. Find Trait Implementations: Look for the line that says “Go to [x] implementations” (where x represents the number of implementations). Press Enter to open a window showing all the traits implemented by that symbol. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:3:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"VSCode: Simplified with rust-analyzer VSCode users can also take advantage of rust-analyzer for similar functionality. Here’s how: Install rust-analyzer Extension: Make sure you have the rust-analyzer extension installed and enabled in your VSCode setup. Navigate to the Symbol: Click or place your cursor on the struct or enum you’re interested in. Open the Symbol Inspector: Press SHIFT+K once. This opens a detailed view of the symbol, including trait implementations. Explore Implementations: Click on the “[x] implementations” link. A new window will appear, listing all the traits implemented by the symbol. ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:4:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"Why This Matters Understanding which traits a struct or enum implements is essential for maintaining and debugging Rust code, especially in larger projects. By integrating rust-analyzer into your workflow, you can overcome Rust’s decentralized trait implementation syntax and make your development process smoother. Whether you’re using NeoVim or VSCode, rust-analyzer empowers you to navigate and understand your codebase with confidence. Try these tips today and experience the productivity boost firsthand! ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:5:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"},{"categories":["rust"],"content":"References [^1] rustaceanvim ","date":"2025-01-04","objectID":"/how-to-check-traits-implemented-for-a-struct-or-enum/:6:0","tags":["rust","beginner"],"title":"Rust Tips: How to Check Traits Implemented for a Struct or Enum","uri":"/how-to-check-traits-implemented-for-a-struct-or-enum/"}]

0 commit comments

Comments
 (0)