wppaste
WordPress

twentyeleven_color_schemes(): array<string,

Since
Twenty Eleven 1.0
Source
wp-content/themes/twentyeleven/inc/theme-options.php:157
Returns an array of color schemes registered for Twenty Eleven.

Compatibility

WordPress
since Twenty Eleven 1.0
PHP
7.4–8.6-dev
  • 6.7.7
  • 6.8.8
  • 6.9.7
  • 7.0.4
  • 7.1.0

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Return value

array<string,
array<string, string>> An associative array of color scheme options.

Performance profile

How much work a call to twentyeleven_color_schemes() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class
Trivial

Touches nothing outside its own arguments.

Scaling
Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions
30

Executed per call on PHP 8.5. The body compiles to 30.

Plugin surface
1 hook

Third-party callbacks on 'twentyeleven_color_schemes' run inside this call, and their cost is not bounded by anything here.

Called by
4

4 places in core call this, so the cost is paid more often than your own code shows.

What it touches

  • hookthird-party callbacksapply_filters()called directly

Further down the call graph this can also reach option, cache, serialize, transient and query. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 1 distinct outcome

One number would be a lie: the work depends on which branch runs. These are every distinct cost twentyeleven_color_schemes() can have, taken from its control-flow graph on PHP 8.5.

WhenInstructionsCalls it makes
always30__(), get_template_directory_uri(), __(), get_template_directory_uri(), apply_filters()

Across PHP versions

Compiles the same on PHP 7.4, 8.1, 8.2, 8.3, 8.4, 8.5 and 8.6-dev: 30 instructions, 30 executed per call, 0 branches. The work does not change between versions.

An instruction is not a fixed amount of time, so a matching count is not necessarily the same speed; what it rules out is a difference in the work itself.

Hooks and filters fired · 1

One hook fires while twentyeleven_color_schemes() runs, in this order:

  1. apply_filters( twentyeleven_color_schemes )filterline 180 (+23 into the body)

    Filters the Twenty Eleven color scheme options.

Uses · 3

Used by · 4

Source code

function twentyeleven_color_schemes() {	$color_scheme_options = array(		'light' => array(			'value'              => 'light',			'label'              => __( 'Light', 'twentyeleven' ),			'thumbnail'          => get_template_directory_uri() . '/inc/images/light.png',			'default_link_color' => '#1b8be0',		),		'dark'  => array(			'value'              => 'dark',			'label'              => __( 'Dark', 'twentyeleven' ),			'thumbnail'          => get_template_directory_uri() . '/inc/images/dark.png',			'default_link_color' => '#e4741f',		),	); 	/**	 * Filters the Twenty Eleven color scheme options.	 *	 * @since Twenty Eleven 1.0	 *	 * @param array<string, array<string, string>> $color_scheme_options An associative array of color scheme options.	 */	return apply_filters( 'twentyeleven_color_schemes', $color_scheme_options );}

Changelog

Introduced in Twenty Eleven 1.0. One change between 6.7.7 and 7.1.0.

  1. 6.7.7
  2. 6.8.8
  3. 6.9.7
  4. 7.0.4
  5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

7.0.4
Return type changed from none to array<string,.verified against source
Twenty Eleven 1.0
Twenty Eleven 1.0from the docblock

About this page

Parsed data
Generated from the wordpress-develop 7.1.0 tag, from src/wp-content/themes/twentyeleven/inc/theme-options.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.
Corrections
Something wrong on this page? Report it and it gets fixed in the next regeneration.