sc::AVLMap...::iterator(3)
β¨ NAME β¨
sc::AVLMap< K, T >::iterator β bestie, this is the iterator type that lives inside sc::AVLMap, and it's giving main character energy in the Library Functions Manual π
π¦ SYNOPSIS π¦
π Public Member Functions π
iterator (const EAVLMMap< K, AVLMapNode< K, T > > *m, AVLMapNode< K, T > *n)
iterator (const eavl_typename AVLMap< K, T >::iterator &i)
void operator++ ()
void operator++ (int)
int operator== (const eavl_typename AVLMap< K, T >::iterator &i) const
int operator!= (const eavl_typename AVLMap< K, T >::iterator &i) const
void operator= (const eavl_typename AVLMap< K, T >::iterator &i)
const K & key () const
T & data ()
okay so let's go through this lil roster one by one, no skipping, because every single one of these is doing something π«Ά
iterator (const EAVLMMap< K, AVLMapNode< K, T > > *m, AVLMapNode< K, T > *n)β the constructor that takes a pointer to anEAVLMMap(the one holdingAVLMapNode< K, T >s) plus a pointer to anAVLMapNode< K, T >. Two args, zero drama β¨iterator (const eavl_typename AVLMap< K, T >::iterator &i)β the copy-ish constructor: you hand it aconstreference to anothereavl_typename AVLMap< K, T >::iteratorand it does its thing. Yes,eavl_typenameis really spelled like that, and no, we are not editing it πvoid operator++ ()β the prefix increment operator. Returnsvoid. That's it, that's the whole vibe.void operator++ (int)β the same increment operator but with that littleintin the parens. Returnsvoidtoo. You know the one πint operator== (const eavl_typename AVLMap< K, T >::iterator &i) constβ equality check against anotherconst eavl_typename AVLMap< K, T >::iterator &i. Comes back as anint, and it's markedconst, so it's on its best behaviour πΈint operator!= (const eavl_typename AVLMap< K, T >::iterator &i) constβ the not-equal version of the above. Same argument, sameintreturn, sameconst. Iconic, honestly.void operator= (const eavl_typename AVLMap< K, T >::iterator &i)β assignment. Takes aconstreference to another one of these iterators, gives you backvoid. Slay.const K & key () constβ hands you aconst K &. It'sconst-qualified, so calling it won't mess with anything. We love a safe queen πT & data ()β hands you a plain oldT &. Notconst. Just saying π
π Author π
Generated automatically by Doxygen for MPQC from the source code. Not a human, not a girlboss, just a documentation generator doing its little automated thing π€β¨
and that's the whole page, bestie π that was MPQC, Version 2.3.1, page sc::AVLMap...::iterator(3) β thank u for coming to my TED talk, now go iterate something π₯π¦
π¦ where this page comes from
- fedora 43: mpqc-devel 2.3.1-65.fc43 Β· GPL-2.0-or-later AND LicenseRef-Callaway-LGPLv2+
- fedora 43: mpqc-devel 2.3.1-65.fc43 Β· GPL-2.0-or-later AND LicenseRef-Callaway-LGPLv2+
- ubuntu noble: libsc-doc 2.3.1-22build2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms