<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Creating a type-safe implementation of the INotifyPropertyChanged&#160;interface</title>
	<atom:link href="http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/</link>
	<description>Sebastian Negomireanu&#039;s Weblog</description>
	<lastBuildDate>Thu, 06 Oct 2011 05:40:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
	<item>
		<title>By: Sebastian Negomireanu</title>
		<link>http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/comment-page-1/#comment-169</link>
		<dc:creator>Sebastian Negomireanu</dc:creator>
		<pubDate>Mon, 21 Mar 2011 14:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/#comment-169</guid>
		<description>Well I am using this mechanism in several large projects (WPF and full Silverlight framework) and so far I could not see any visible performance penalty (also the profiler did not report these expressions as hotspots). Since the expressions are used in a short scope, they won&#039;t reach Gen 1 or Gen 2 so they will be quickly collected.</description>
		<content:encoded><![CDATA[<p>Well I am using this mechanism in several large projects (WPF and full Silverlight framework) and so far I could not see any visible performance penalty (also the profiler did not report these expressions as hotspots). Since the expressions are used in a short scope, they won&#8217;t reach Gen 1 or Gen 2 so they will be quickly collected.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is the run-time cost?</title>
		<link>http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/comment-page-1/#comment-168</link>
		<dc:creator>What is the run-time cost?</dc:creator>
		<pubDate>Fri, 18 Mar 2011 15:24:39 +0000</pubDate>
		<guid isPermaLink="false">http://byteflux.me/index.php/2009/08/17/creating-a-type-safe-implementation-of-the-inotifypropertychanged-interface/#comment-168</guid>
		<description>I am worried about the run-time cost. If you have many property changed notifications, you will use a lot of Lambda expressions and instantiate lots of Expression&lt;Func&gt;. How will the garbage collector react to creating and destruction of all these small objecs. Using SilverLight on WindowsPhone the garbage collector will halt everything and collect when needed.</description>
		<content:encoded><![CDATA[<p>I am worried about the run-time cost. If you have many property changed notifications, you will use a lot of Lambda expressions and instantiate lots of Expression&lt;Func&gt;. How will the garbage collector react to creating and destruction of all these small objecs. Using SilverLight on WindowsPhone the garbage collector will halt everything and collect when needed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

