You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rust.tex
+11-2Lines changed: 11 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2632,19 +2632,28 @@ \section{Object-Oriented Programming Features of Rust}
2632
2632
\item Inheritance is a mechanism whereby an object can inherit elements from another object’s definition, thus gaining the parent object’s data and behavior without you having to define them again.
2633
2633
\begin{itemize}
2634
2634
\item If a language must have inheritance to be an object-oriented language, then \textbf{Rust is not one}.
2635
-
\item You can do this in a limited way in Rust code using default trait method implementations.
2635
+
\item You can do this in a \textbf{limited way} in Rust code using default \textbf{trait} method implementations.
2636
2636
\end{itemize}
2637
2637
2638
2638
\end{itemize}
2639
2639
\end{frame}
2640
2640
2641
2641
2642
2642
\begin{frame}[fragile]
2643
-
\frametitle{Encapsulation}
2643
+
\frametitle{Encapsulation that Hides Implementation Details}
2644
2644
2645
2645
\begin{itemize}
2646
2646
\item Another aspect commonly associated with OOP is the idea of encapsulation, which means that the implementation details of an object aren’t accessible to code using that object.
2647
+
\item Therefore, the only way to interact with an object is through its \textbf{public} API.
0 commit comments